On 15/05/2008, at 7:43 AM, Andrus Adamchik wrote:
> 1. Client sends a "give me events" request in the beginning of the
> session (separate from data requests), and reads everything that
> comes back.
Three thoughts:
1. Is your idea to have one queue per client, or a single queue with
some sort of sequence numbering so a client can grab events later than
a particular timestamp/sequence?
2. Even without continuations the basic idea could still work if the
client received these events attached to query results. So every time
a client performs a query (or executes a special polling request)
these events are received. Not quite so real-time, but possibly useful
in many circumstances.
3. Are the events here just refresh query cache events, or are we
talking about 'invalidate record id 1234 from entity Artist' messages?
Possibly that will generate too much traffic since the server will not
know which clients have those entities already cached and will have to
propagate all invalidate messages to all clients. I'm still a little
hazy about whether the server has a copy of the same contexts as the
client does, so perhaps it does know which records the client is
holding, but I'm not sure how SHARED_CACHE impacts that.
Ari
-------------------------->
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
This archive was generated by hypermail 2.0.0 : Thu May 15 2008 - 05:27:34 EDT