The time spent by the compiler compiling an app will dwarf any I/O overhead I think, even disk I/O. I would do some measurements before making any assumptions...
On 11/2/07, Volkan YAZICI <[EMAIL PROTECTED]> wrote: > Jean-Baptiste BRIAUD <[EMAIL PROTECTED]> writes: > > In fact, the OL servlet accept on the file system any lzx file. > > Then, via HTTP, on the first acces it become compiled and the HTTP > > deliver the swf content. So, there is nothing to do. You "just" > > write your lzx file under the web root folder (in that great LISP > > language for eg), then, you compute the URL corresponding to this > > file and from HTTP client you get the SWF result (or DHTML). > > I don't think that would be a plausible solution when you consider the > redundant I/O overhead and ugly design. But thanks for your opinions. > > I'd probably try implementing a standalone Java server listening > incoming TCP connections and communicating via some basic binary > protocol (msg length, msg, output format, etc.), or switch using SWIG. > > I also need to find out whether org.openlaszlo.compiler.Main handles > caching for me or I'll need to create an extra memcache layer between > server and clients. > > > Regards. > -- Henry Minsky Software Architect [EMAIL PROTECTED]
