Philip Eskelin wrote:
>
>...
>
> I'm not sure where my version of this verb/URI issue stands, but here is the
way
> I have designed it in my own efforts. As I mentioned before, I have a
> pre-developed set of resource types, namely methods, components, topics,
queues,
> etc that are published in a node's hierarchical namespace.

I guess the basic question is whether you *need* method objects. A
REST-purist view would be that you should use methods as an
implementation technique to implement a resource view of the world.
Since I don't know what method objects you have, I can't
resource-decompose them. But in most cases you will want an action to
have a side-effect that creates a resource+URI, and you will want the
newly created resource to be in some container. So you can instead use a
POST on the container.

>...
> HTTP PUT - instead of getting a pre-existing resource like the one above, it
> allows you to effectively copy a resource in its current state to another
node.
> You are effectively publishing it on the destination node.

It's not clear to me how you can copy a method. After all, the real
method is the programming code behind it. And that code will depend on a
complex network of other state. So PUT-ting to a method resource doesn't
make much sense to me.

Paul Prescod