Hi Gabriele, This is a common misunderstanding that I'll put in the FAQ.
Polling is done on the client side! It merely checks if all data has arrived on the client! What Rugby does: - You open a deferred request and get a ticket number. This is a non-blocking , not-buffered port - Whenever you 'poll' using result-ready? the client reads whatever data is available, and checks if the message is complete. If the message is complete, result-available returns false, otherwise true and you get the result by calling get-result. Put this in an event queue, do the ordering of the messages correct and you have Gorimnb ;-) NOTE: you are programming asynchronously which is, well, different. Ask Graham ;-) You can write your own Rugby client that integrates this with a wait on the fastcgi ports, assembles the data, checks to see if it is complete and updates the wait list accordingly. HTH, Maarten > Maarten Koopmans wrote: > > Now you return listening on the fastcgi port and periodically check if > > the result has already arrived. > > Do you need polling the rugby server? Would it be possible to just > wait on the tcp port? > > Just being curious, > Gabriele. -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
