Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Application-Level Queue, Server-Push, etc.
January 20, 2008, 6:57 pm
rate this thread
of chat - in which a few different processes will generate data and
one or more http clients will need to be notified. (Something like
this was used at http://ajaxian.com/archives/the-broth-ajax-shared-mosaic
-- but that appears to be very specific to their problem area and I'm
interested in something more generic.
"Slow load" (see http://www.obviously.com/tech_tips/slow_load_technique )
seems a good mechanism to notify the client, but the simple form of
that needs build up to accommodate events of several types from a
number of sources.
It looks to me that application-level script-to-script notification is
needed - and exists (see http://www.leosingleton.com/projects/code/phpapp /)
plus a queue mechanism, which also exists (see http://www.phpclasses.org/browse/file/5025.html )
I've googled for it and failed to find a packaging of these elements.
I'm interested in hearing about any that might exist, before I try to
roll my own. Thanks, all.
- C. (http://symcbean.blogspot.com/)
January 21, 2008, 12:38 pm
Re: Application-Level Queue, Server-Push, etc.
I'd start by forgetting about the suggestions in
http://www.leosingleton.com/projects/code/phpapp/ this is *so* not the
way to solve either your problem or the one described on the page.
Most message queueing systems are based around providing transactional
integrity - and you're going to get tied in knots trying to get this
to work for a browser based system ( where you can't guarantee
notification of the end of a session).
Sorry I've got nothing positive to add - but I can't see any solution
other than starting from scratch - but yes, using ajax to poll a
deferring page is probably the way to go.