On Mon, 7 Mar 2005, Perrin Harkins wrote:
> Cahill, Earl wrote:
> > 1. TT parses the page and does all tags, except those containing a
> > priority
> > 2. I get, say, an array ref of hash refs, corresponding to the tags
> > for an entire page (since priorities don't necessarily match
> > layout order),
> > 3. my stuff handles the priorities and make the calls in parallel,
> > waiting for calls to finish appropriately
> > 4. I pass the array ref back to TT for interpolation, with variables
> > set in my code available to TT
>
> It would all be much simpler if step 1 was that your code looks at some
> kind of user preferences data to see what should be on the page, and TT
> didn't enter the picture until step 4. That would also let you build
> clean code for generating the content data, which could make smart use
> of caching for things like your "geo" data. It would be an ordinary
> forking and IPC programming exercise.
You could also try pushing some of the parallel processing back onto the
browser by embedding the chunks in IFRAMEs within your main page, where
e.g. one IFRAME pulls in the weather chunk and one pulls in the movies
chunk, each as individual URLs. It would mean more hits on your server,
but could still take advantage of cached content.
Larry
p.s. Perrin:
My PC-Pine spell-checks your last name as "Hacking" - how apropos...
:-)
|
