Hi!

This is a call for discussion. My current project involving big web forms 
(selects having tens or hundreds of entries, all fields explained by title="" 
attributes, ...) has a definite slowness experience. Using precaching, XSP 
execution time is 1-2 seconds, that's okay, but it takes 5 seconds after 
axkit declares delivery in the logs until the browser shows anything 
(everything at once, to be exact).
One big advantage of PHP, CGI, ... is the ability to send the http headers and 
some content ahead of the rest - even before the main grunt of processing 
started. It makes AxKit appear a lot slower, although it isn't.

My question: how can AxKit accomplish (something similar to) that?

My only idea so far would be to use a classic sandwich-template system and 
integrate AxKit through Apache::Filter. Which would mostly defy the reason to 
use AxKit. Send-Ahead is only useful for noncacheable resources.

Please tell me your ideas, they may be a bit academic, hard to implement, or 
not possible right now, still I'd like to hear them.

-- 
CU
   Joerg

Reply via email to