Am 20.03.15 um 07:48 schrieb Sep Ng:
what is hurting you?
We have instances where we'd get a high number of concurrent users
that the requests are getting queued, but when I look at the logs,
there's a lot of static files being served for each login page, let
alone other pages being
Thank you once again for your swift response!
On Friday, March 20, 2015 at 2:33:59 PM UTC+8, Gustaf Neumann wrote:
Am 20.03.15 um 05:47 schrieb Sep Ng:
Hi Gustaf! Thank you for the informative response!
I've been thinking of moving to NaviServer but I don't know enough about
the
Thank you very much for shedding a lot of light into this.
On Friday, March 20, 2015 at 3:58:19 PM UTC+8, Gustaf Neumann wrote:
Am 20.03.15 um 07:48 schrieb Sep Ng:
what is hurting you?
We have instances where we'd get a high number of concurrent users that
the requests are
Am 20.03.15 um 05:47 schrieb Sep Ng:
Hi Gustaf! Thank you for the informative response!
I've been thinking of moving to NaviServer but I don't know enough
about the transition to make that call yet. Right now, we're on
aolserver and so, I'm trying to see what I can do on this platform. I
Scheduling isn't needed. I read your question again and I understand
what you're looking for. You're asking for all the javascript and
images on a page to be sent in one request correct? You'll need to find
a way to buffer the output and then parse and change the buffer before
it's sent. It
Dear Sep,
The question whether it is worth to use asynchronous delivery boils
down to a question of usage pattern and desired scalability.
The general problem with serving (large) resources via
classical aolserver is that a connection thread is unable
to handle other threads for the time span of
Hi Gustaf! Thank you for the informative response!
I've been thinking of moving to NaviServer but I don't know enough about
the transition to make that call yet. Right now, we're on aolserver and
so, I'm trying to see what I can do on this platform. I do not understand
why the delivery
