Re: [DotGNU]Message passing between webservices

[Peter Minten]

Chris Smith wrote:

> You can't just let the method be exposed by default because the name of it
> will probably not be appropriate for a webservice method.  Also when you
> write a class it generally has a lot of methods in it, but only a handful are
> publishable.  You should force the author to explictly publish what they
> intend to publish.

Makes sense.
 
> There may be a way to automate the publishing of 'properties' by providing a
> special attribute for this purpose and having it do the necessary behind the
> scenes.  DotGNU specific yeah - but we want to make the world a better place.
> Externally property access looks just like member access (and so it should!)
> so Xml-Rpc and thus all protocols will be fine.

Yes!

> Yes it will <grin>.
> If you want state, then the webservice is built to provide state (ie the
> state property of the WebService attribute is set).  This has the effect of
> making the object/class serialise itself on destruction (or at the first
> point at which execution leaves the class).  The object is serialised to some
> central storage shared by the execution environment.  This is all done for
> you.
> 
> The original caller (who did the set) gets a session reference back.  When
> they do the get_ call, the session reference is sent too enabling the
> execution environment to restore its state and satisfy the request.

Remember the service level plan? You don't want to send a new session reference
every time if you can suffice with one session key. That won't be much of a
problem with DGEE I guess and is much more consistent.

Greetings,

Peter