Skip to main content

This post is not so much a cry for help but the attempt to start a discussion.


I just started to call webservices and the tool to use - according to this forum - was rmnet.

So I managed to call HTTPPOST and HTTPGET and was pretty happy.

Until I was asked to call a webservice with the method PUT.

I tried, failed and asked the support. They sent me a link to a 6 year old post (community.microfocus.com/.../1726138 where the author basically said:

PUT and DELETE are not supported, use curl instead.

My colleague - the creator of the webservice I have to call - says the only difference between POST and PUT is the word PUT in the call instead of POST.

So does anybody know why rmnet does not support PUT ?

Can't this dll be changed ? What has to happen that microfocus changes the dll ?

I find it so strange (not to say ridiculous) that rmnet supports the creation but not the update and the offered solution means a totally new workflow (to learn a new language, create a file with the call, make a systemcall, redirect the answer to another file, read this file to get the result etc.)

Had I known this earlier, I would have worked with curl instead of working with rmnet in the first place.

Did you have a similar experience ?
Do you have interest in a library that supports the minimal requirements ?
Do you have other issues that bother you ? I think of the bug that the COPY REPLACING is not performed in the listing nor the debugger.

 

 

This post is not so much a cry for help but the attempt to start a discussion.


I just started to call webservices and the tool to use - according to this forum - was rmnet.

So I managed to call HTTPPOST and HTTPGET and was pretty happy.

Until I was asked to call a webservice with the method PUT.

I tried, failed and asked the support. They sent me a link to a 6 year old post (community.microfocus.com/.../1726138 where the author basically said:

PUT and DELETE are not supported, use curl instead.

My colleague - the creator of the webservice I have to call - says the only difference between POST and PUT is the word PUT in the call instead of POST.

So does anybody know why rmnet does not support PUT ?

Can't this dll be changed ? What has to happen that microfocus changes the dll ?

I find it so strange (not to say ridiculous) that rmnet supports the creation but not the update and the offered solution means a totally new workflow (to learn a new language, create a file with the call, make a systemcall, redirect the answer to another file, read this file to get the result etc.)

Had I known this earlier, I would have worked with curl instead of working with rmnet in the first place.

Did you have a similar experience ?
Do you have interest in a library that supports the minimal requirements ?
Do you have other issues that bother you ? I think of the bug that the COPY REPLACING is not performed in the listing nor the debugger.

 

 

An HTTP POST is more general. It is supposed to initiate an action on the server. 

PUT is like a file upload. A put to a URI affects exactly that URI. 

I cannot answer why PUT and DELETE are not part of RMNet. 

One way to start a conversation with the Development team is by contacting Customer Care and requesting a Suggested Feature. Also, your Sales person may be able to discuss your request with Development.

It's possible that since curl provided this capability, the team decide not to rewrite what was available in curl into RMNet. I have no knowledge of those decisions, just guessing.

 

Terms & ConditionsAccessibility statement