At 13:45 -0500 02/04/2002, Jason Gruhl wrote:
>I am trying to decide whether or not to use Shockwave for a web app
>that I am writing. My one concern is shockwaves ability to do
>multi-threaded sort of tasks. Basically what I envision is a user who
>interacts with the application while the application is constantly
>talking to a server and updating data which is displayed on the
>screen. What do you think about shockwave compared to say a java
>applet.
Wow, I don't think I'd really want to try sWave for that, but then
I'm not sure how suitable Java would be either! :\
What do you mean by 'constantly' talking to a server? If you mean
literally -- the app and the server must be in incessant
communication -- I'd recommend against the design entirely unless you
were hardwired. It's too easy to imagine situations where things
might go terribly wrong, or at least terribly slowly.
--
Warren Ockrassa | http://www.nightwares.com/
Director help | Free files | Sample chapters | Freelance | Consulting
Author | Director 8.5 Shockwave Studio: A Beginner's Guide
Published by Osborne/McGraw-Hill
http://www.osborne.com/indexes/beginners_guides.shtml
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
