callRemote syntax for operations

[Jonathan Lange]

Programmers who are used to Twisted are used to using a syntax like:
  d = object.callRemote('operationName', arg1, arg2, named=valued)

when doing remote procedure calls. It would be nice if txrestfulclient supported such a syntax.

Other than the benefit of familiarity, the syntax also highlights network operations. In many programs, it matters a great deal whether a particular operation is networked or remote.

[James Westby (james-w)]

Shouldn't be too hard to implement.

At least in txrestfulclient you get Deferreds to remind you. I agree it
would be useful to be able to be more explicit though.

What about attribute lookop and the like? Should that have a callRemote
syntax too?

Thanks,

James

[Jonathan Lange (jml)]

On Mon, Jun 7, 2010 at 6:18 AM, James Westby <email address hidden> wrote:
...
> What about attribute lookop and the like? Should that have a callRemote
> syntax too?

I don't know, actually. I thought attribute lookup was always a local operation?

jml

[James Westby (james-w)]

It is, but there is lp_resolve to trigger the network access, it would be possible to
combine the two steps using callRemote.

Thanks,

James