[Spread-users] Initial implementation of XMLRPC over Spread
John Schultz
jschultz at d-fusion.net
Fri Oct 10 12:59:29 EDT 2003
Will your well known group be served by multiple servers? If not, then
FIFO should be all that you need.
--
John Schultz
Co-Founder, Lead Engineer
D-Fusion, Inc. (http://www.d-fusion.net)
Phn: 443-838-2200 Fax: 707-885-1055
Yair Amir wrote:
> Hi G.P.,
>
> I have a question: what property of a SAFE message do you need that
> AGREED message does not give you? The reason for me asking is that for
> many usages AGREED message is fine. Agreed message incurs aprx.
> 1/4 to 1/3 of the latency of a SAFE message.
>
> Cheers,
>
> :) Yair.
>
> On Friday, October 10, 2003 4:04 AM
> g.p.ciceri g.p.ciceri gp.ciceri at acm.org wrote:
>
> g.p.ciceri> Hello all,
> g.p.ciceri> I've just setup a little python implementation
> g.p.ciceri> (a simple server class and a client test program)
> g.p.ciceri> of XMLRPC calls over a Spread (http://www.spread.org)
> g.p.ciceri> communication group.
>
> g.p.ciceri> It's rather crude; from a private msgbox you send a SAFE
> g.p.ciceri> message (coded in XMLRPC syntax) to a well-known group
> g.p.ciceri> acting as (server) endpoint.
>
> g.p.ciceri> From a server listening to this endpoint you send another
> g.p.ciceri> SAFE message back to the client with the XMLRPC response.
>
> g.p.ciceri> As method to reduce group communication noise
> g.p.ciceri> there's a filter on the messagetype: I've used type 006
> g.p.ciceri> to tag message for rpc processing.
>
> g.p.ciceri> Error handling is non-existant, so is documentation.
>
> g.p.ciceri> You'll find it at http://pyhacks.suddenthinks.com/index.html#20031010
>
> g.p.ciceri> Any comment will be appreciated, as usual.
> g.p.ciceri> Regards
> g.p.ciceri> /gp
>
>
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users
>
More information about the Spread-users
mailing list