> Flash with XMLSockets or FlashComm will give you an always-on
> connection.
> Any use of a webserver on the client machine to provide local
> "back-end"
> functionality to a desktop app is really overkill.
>
Ya' know, the more I think about it ---
Logically you are correct!
But in practice, I think the browser may be better -- at least from a
performance standpoint.
On my Mac 1 GHz G4 1 Gig RAM
I normally run
Apache
Jetty web server
JRun
CFMX for J2EE
BDJ2ee
MySQL
SyBase_ASE
Safari
FireFox
Mozilla
Email Client
Terminal CLI
BBEdit IDE
various desktop programs
Activity Monitor
Now, the secret to all this running at once, is that nothing uses much
system resources unless it is actively being used -- the components
just sit there taking up virtual memory and and a few hunddreths of a
cpu cycle.
For example, 1 Have 1 FireFox window open to Apple's main page
www,apple.com ------ 0.5 - 2.4 CPU & 28.34 MB real memory
now if i point that browser to macromedia
www.macromedia.com ----- 16.0 - 24.7 cpu 35.38 MB real memory
so, open up another window to the flex code explorer (pops up a 3rd
window)
now total firefox is 31.9 -38.5 cpu and 71.83 cpu
None of the 3 windows is active or visible, but Flash is gobbling up
1/3 of my cpu cycles just lookin'for something to do.
I suggest to you, that Flash, in its current implementation, is
overkill!
I can do a lot more, and much better by running another server or
daemon. They don't use many cpu cycles until they *find* something to
do.
HTH
Dick
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
