Hi Ian,

> I might play around with object publishing in Webware using this... the
> implementation seems fairly simple.  Anyway, I'm interested in feedback
> too, which is why I posted here in the first place ;)

I'm neither an Webware nor an XMLRPC expert, but I have some experiences
with SOAP. In my opinion, your design hits some problems which are not
solvable in a general fassion. I'll try my best to explain it (but keep in
mind that I'm not a native speaker, so feel free to ask if something is not
clear):

What you try to build is some kind of statefull XMLRPC protocol. There are
already technics to do this: COM, CORBA, ... but they have their own
problem. XMLRPC and SOAP were build with fast, stateless single calls in
mind to work around the problems of COM and CORBA. The main problem of COM
and CORBA is, that somebody has to manage the object. The liftetime of the
object is usually managed on the server, but then you have a problem if the
connection breaks. Using XMLRPC and SOAP you can not realy hold objects on
the server, so you have to manage the objects on the client. To do this, you
store the state information of the object on the client and send it to the
server each time you call a method. In your example, this is only the id,
but it could be a lot of other state informations. Sending all this
information all the time would produce a lot of useless network overhead. In
general you can not decide, if property x affects a call to method y.

What MS propagates in this context makes very much sense to me: Build
complex bussines logic in a closed LAN, where you can use COM or CORBA and
expose small, stateless functions to the outher world. Of course, I would
prefere to use Python and CORBA and not .NET! ;-)

I hope this was a little bit understandable. If not, please point me to the
unclear parts.

Achim



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to