Yes SOLO will be safer and more efficient. It is the recommended way
to publish your application.
On 2009-07-21, at 05:37EDT, Chen Ding wrote:
I am sure the tomcat server was not crashed because if the button
did not
show up, if I reload the file again, the button might show up. It
was just
not that certain that the application would be loaded.
Thanks for your recommendation. Here is what I did. I clicked the
"SOLO"
button for the "Deploy:" option. It popped up a dialog that
generated a swf
file for the application. If I load the swf file instead of the
"lzx" file,
that will not go through the "compiler", and that will be safer and
more
efficient. Is this understanding right?
Thanks!
Chen Ding
On Mon, Jul 20, 2009 at 10:23 PM, P T Withington <[email protected]>
wrote:
I'm only aware of this ever happening if the tomcat server crashes,
so you
might want to look at your tomcat logs.
We highly recommend that deployed applications be compiled in SOLO
mode so
that you eliminate the overhead (and possible security issues) of
running
the tomcat-based compiler. The tomcat server and compiler are really
intended only as a development environment.
On 2009-07-20, at 00:30EDT, Chen Ding wrote:
Hi there,
It appears that when we load an lzx file, the system may fail
loading
(i.e.,
not showing anything). Below is an example:
<canvas>
<button text="testing"/>
</canvas>
Try to load (and reload) this file multiple times. Sometimes, the
button
does not show up at all. This makes us worry very much. We are
going to
roll
out our applications. This will simply kill the whole project.
It happened occasionally in the past, but we did not pay much
attention to
it, thought it might be our fault.
We are running 4.4.1, but the same problem appears in at least
4.3.1.
Your help is greatly appreciated!
Chen Ding
