On Tuesday, 04. February 2003 20:47, Tom Howe wrote: > Since every page request requires the users session to be pulled from > the database and the sessions can (occassionally) be over a meg its > important that the messaging system is quick and so far we havnt had any > problems. In fact the bottleneck in our system is definately XPathScript > rendering and the way we generate our XSP pages on the fly. The load on > our webservers is much higher than our application servers.
Hah! Gotcha! I knew there must be others who generate their XSP on-the-fly while knowing what they do. :-) I am doing that, too, and plan to revise AxKit's XSP caching. Currently, the generated code is not cached if it's not directly from a provider. My question is: Is your code cacheable, and what determines if it is up-to-date? This can be a major time-saver as generating and eval'ing the code is not neccessary on a cache hit. I'd love to take your requirements into account when going in there. -- CU Joerg PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
