[Laszlo-user] laszlo app behind a symlink

[P T Withington]

On 2007-06-11, at 17:22 EDT, Vincent de Phily wrote:

> 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).

I think most developers develop their app in server mode and only  
switch to SOLO at the last minute.  What you will miss there is that  
swf cannot handle some media types, and you will only discover that  
when you switch to SOLO mode.

> 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.

Another approach is to use lzc as a command-line compiler and set up  
a build system for yourself that automatically installs the output  
into the right place in an Apache server so you will be testing in  
something closer to your deployment environment.  I know there are  
people doing that, but there is little documentation on how to do that.