[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [DotGNU]Message passing between webservices

From: Chris Smith
Subject: Re: [DotGNU]Message passing between webservices
Date: Sat, 11 Jan 2003 17:55:24 +0000

On Saturday 11 January 2003 16:39, Peter Minten wrote:

> [mp]
> [description="Example class"]
> class Foo
> {
>   [description="DotGNU RULES"]
>   public int A
>   {
>     [description="Get value, returns null if value > 10"]
>     get
>     {
>       return value
>     }
>     [description="Set value, returns exception if value > 10"]
>     set
>     {
>       a = value
>     }
>   }
>   [description="The next big thing after A"]
>   public void B()
>   {
>     //Do something
>   }
>   [mp=false]
>   public int C()
>   {
>     //Do something
>   }
> }

Very similar to the DotGNU.XmlRpc stuff shipped with the DGEE - and is a 
great idea.

What I've been intending to do is creating a base interface class which is 
what does the comms with the DGEE.  This class is then derrived from to 
create XML-RPC interfaces, and would also be derrived from to create a Jabber 
interface, and the one you've outlined above.

Basically, I was going to get the XmlRpc class stuff done, then split it into 
a base layer and an XmlRpc layer.

Then we've got an extensible model - and the abstraction that is absolutely 
necessary and _mandatory_!

Thus total integration is guaranteed.
The base interface class can be changed if the low level transport stuff 
changes without affecting the application side.

So, there *is* work underway to provide this sort of thing (actually to 
support anything you think of, dotgnu mp, soap, jabber, xml-rpc, etc) and 
that work needs to get a little more mature before we can start really 
implementing protocol handling in anger.

Oh - the Attribute set needs to be standardised for the introspection to work 
properly (and to produce consistent documentation) - though we do have a lot 
of room to manouver with this one.

It's great that people are heading in the same direction !! yay!


Chris Smith
  Technical Architect - netFluid Technology Ltd.
  "Internet Technologies, Distributed Systems and Tuxedo Consultancy"
  E: address@hidden  W:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]