On Monday 11 June 2007 20:38:38 P T Withington wrote: > No hidden hint. In non-solo mode for swf runtime, the Laszlo JSP > acts as a proxy for some media files, transcoding them to a format > acceptable to the swf runtime. I was guessing that the problem might > lie in these proxy JSP's. But from the rest of this thread, it > appears that it is tomcat problem. > > Have you actually deployed your SOLO app as a static file? I would > think then it would suffer from the same problem as your other static > files.
I actually haven't deployed it yet. Wether that non-deployed state can still be called "solo", I'm not here to judge :p But that explains why *.lzx and *.* can behave differently. I'm still in early stage of devellopment, and deploying the app everytimeI change a coma in the code sounds like a time-killer (arguably, I never played much with the dep[loyment facilities). Then again, the current opinion with the guys who will deploy my app is that they'll compile the SWFs and serve them through apache (the app's backend is python running on apache). So in trying to get the thing to work with tomcat, what I really want is to save devellopment time. -- Vincent de Phily
