Re: Bidirectional RPC

>Von: Jay Carlson <[email protected]>
>An: [email protected]
>Gesendet: Donnerstag, den 16. Juli 2009, 13:01:48 Uhr
>Betreff: Re: [xml-rpc] Bidirectional RPC
>
>>You could consider having a getNextEvents service available; clients would
>>call it, and get back an array of the most recent events ready for delivery
>>to them.  The clever bit would be that the server would not immediately
>>answer with an empty array; it would stall for as long as it could before
>>returning the empty array.

This is another option that I was considering. But it needs two connections per client/server pair, doesn't it?
If the server is executing (=idling most of the time) a getNextEvents from the client, and during that idling the client needs to send a different request to the server, it has to open a second connection. Not a big problem, but at some point this will half the possible number of connected clients.

Do you see a possibility to communicate bidirectionally following your suggestion, while having only a single connection open? Probably it's a limitation of the HTTP protocol that prevents us from doing this in an efficient way - I don't know enough about network basics to judge this. So I'll probably go for the jsonrpc suggested in another reply.

Thank you!
A. Kalaghan



      


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/xml-rpc/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/