Henrik is completely right about your idea being beyond the scope of what memcached is, but what you might want to look at is something like a Javascript XMPP library (http://blog.jwchat.org/jsjac/ for example). What you're talking about is basically a publish/subscribe model in the browser, and using XMPP would allow you to avoid reinventing the wheel in a couple of places.
- Marc On Mon, Feb 16, 2009 at 6:34 AM, Henrik Schröder <[email protected]> wrote: > Memcached is good because it does one thing, and that one thing very well. > What you want is something different, and the best way to solve your problem > is to find a piece of software that does that other thing. In your case, you > should probably be looking for a message queue instead of trying to convert > a distributed cache into something it is not. > > > /Henrik > > > On Mon, Feb 16, 2009 at 10:24, luka8088 <[email protected]> wrote: > >> >> Hi, i have one idea, for programs (scripts) that run for a very long >> time, and need to check for the same variable on memcached server >> multiple times, to be able to tell server: tell me when a certain >> variable changes... >> >> For example: If we want to make an ajax chat server, then we could >> make ajax request hang in background until someone writes something... >> or, until some variable changes, in this case a loop getting a same >> variable is required, and implementing this option in protocol would >> decrease trafic, because client would not ask server over and over >> again the value of that variable, but instead would wait for server to >> tell him ... >> >> I think this would be best solution for chats and something like that, >> if there is some other way that i don't know of, please let me know, >> because I need it :) >> >> Thank you ! :) > >
