Re: Transparent task to task

On 6/3/2025 8:26 PM, Lawrence D'Oliveiro wrote:

On Tue, 3 Jun 2025 11:23:06 -0400, Arne Vajhøj wrote:

It is true that a HTTP GET can result in different actions: web server
returning static HTML, web server running code that produce dynamic HTML
without changing anything, web server running code that produce dynamic
HTML and do change something.

 Ah, now you’re getting into something called “REST”, where HTTP is being
used essentially as a sort of RPC mechanism.

It applies to both web apps and web services and to any
web service style - RESTful or RPC (RESTful is not RPC).

This involves the addition of more commands besides GET and POST: you also
have PUT and DELETE (and possibly others as well). GET is not supposed to
cause any (user-visible) state changes; it’s only supposed to return info.
As I understand it, POST is supposed to be the mechanism for creating
objects, PUT is supposed to be used for changing the state of objects, and
DELETE is to be used for deleting objects.

And POST is expected to return the created object.
That is how a well behaved RESTful web service should be.
Some also support PATCH for a single request doing the equivalent of
multiple low level PUT's. But one need to be careful about PATCH, some
in between boxes (proxies, firewalls etc.) does not support them.

But not sure that I see the TYPE command being similar to a HTTP GET.

 As pointed out already, it’s not the fault of the TYPE command, it’s the
fault of the underlying comms architecture that allows for this behaviour.
It works with any other command that can open an arbitrary user-specified
file through the same API layer (i.e. RMS).

Yes.
Arne