eviho17
12-14-2006, 07:42 AM
Hi,
I have searched this forum for a solution but couldn't find what I was looking for.
We are deploying an openLaszlo based applicaiton in server mode (proxied=true).
With time the applicationh had gotten quite big.
As for the moment our customers are satisfied with the finalized version except for one thing: Inital compile time:
Just to make order:
When you deploy a Laszlo based application in server mode, it transfers all media (.gif, .swf, .lzx) to requesting cilents (requesting browsers) in a binary format, then it loads the application. When clients (web browsers) approach the server again, they do not have to reload all binaris (they are already in cache), thus they'll only load the application. Whenever you (the developer) upload new .lzx files to your laszlo server, the whole procedure starts again: requesting browsers first request all binaris and then load the application.
Problem:
The time it takes a client (a web browser) with a broadband connection to get all binaris is HUGE. It takes 35 to 45 seconds!!! The loading process (once all binaris arrive)is negligible. It take about 5 seconds. 35 to 45 seconds means ANGRY customers who will not wait that long. It is true that the next time they'll approach the application it will take them much faster to see it (only loading time = 5 seconds) but once we, the developers, will upload a new version (these days we do it a lot). The whole procedure will start again: 35 to 45 seconds to see the application.
Any ideas on how to significantly decrease the inital approach process? This is crucial to the success of our openLaszlo based project.
Thanks,
Eviho17
I have searched this forum for a solution but couldn't find what I was looking for.
We are deploying an openLaszlo based applicaiton in server mode (proxied=true).
With time the applicationh had gotten quite big.
As for the moment our customers are satisfied with the finalized version except for one thing: Inital compile time:
Just to make order:
When you deploy a Laszlo based application in server mode, it transfers all media (.gif, .swf, .lzx) to requesting cilents (requesting browsers) in a binary format, then it loads the application. When clients (web browsers) approach the server again, they do not have to reload all binaris (they are already in cache), thus they'll only load the application. Whenever you (the developer) upload new .lzx files to your laszlo server, the whole procedure starts again: requesting browsers first request all binaris and then load the application.
Problem:
The time it takes a client (a web browser) with a broadband connection to get all binaris is HUGE. It takes 35 to 45 seconds!!! The loading process (once all binaris arrive)is negligible. It take about 5 seconds. 35 to 45 seconds means ANGRY customers who will not wait that long. It is true that the next time they'll approach the application it will take them much faster to see it (only loading time = 5 seconds) but once we, the developers, will upload a new version (these days we do it a lot). The whole procedure will start again: 35 to 45 seconds to see the application.
Any ideas on how to significantly decrease the inital approach process? This is crucial to the success of our openLaszlo based project.
Thanks,
Eviho17