[Pydispatcher-devel] Re: dispatcher over xmlrpc

[Drew P. <dr...@bi...>]

> drewp, on sending dispatcher events over XMLRPC:
> > Worse, however, is that because you take id() of the sender before
> > storing/lookup in the receiver mapping, I can't even use strings as
> > senders because their ids are different in my client and server. So
> > unless that changes, senders are unsupported in the xmlrpc tunnel (not
> > the end of the world).
> 
> Let's look at this again, now that we've got the code in SourceForge.

Indeed. I think the straightforward fix is to stop using (or sometimes
stop using) the id() optimization. There are other ways the XML-RPC
design could go, though.  I may not be able to do a lot of research on
this problem too soon, unfortunately.  

I will point out, though, that the XMLRPC bridge worked like a champ for a
live presentation I did in March.  One process did the displaying of the
presentation, and another process showed me a control panel I could use
to drive the main presentation, the video clips, and the other special
tricks. GSD made things -very- convenient.

-Drew 
(I'm on the list now)