[REBOL] Re: Rugby / TCP woes
From: petr:krenzelok:trz:cz at: 27-Nov-2001 18:08
Maarten Koopmans wrote:
>Hey,
>
>See below....
>
>>Is that right so far? And now - what is the problem for e.g. for chat
>>server, to redistribute (insert-to-port) messages to each client port
>>registered, instead of letting clients to poll the server? And btw- what
>>does polling mean here? Is server contacted with new connection? As becuase
>>I just looked at
>>'http-result-available? function, and it seems to me, that you only do
>>'copy on port, or is there really reconnection happening to the server?
>>
>
>Yes. result-available? reads data from the client port (the *client* TCP
>stack) and does *not* poll the server. If it sees that it has all the data
>(=the return data) it closes the underlying port once you read it in the
>application.
>
>So: all requests use the same port for request/return. In fact,
>wait-for-result is just:
>
> until [result-available? index get-result index]
>
>Then the mysterious httpr (r for rugby) is just a copy of RT's http protocol
>that does not wait for the first two lines of the return header. Truely
>non-blocking. Drawback: you loose automatic http redirects and such. You get
>the complete http response back, so you can implement that yourself.
>
ehm, then you do reuse already opened ports. So how does your aproach
here differes from persistent connection you had in mind???
Thanks,
-pekr-
