Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!bcm.tmc.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!chi-news.cic.net!nntp.coast.net!torn!nott!cunews!tina.mrco.carleton.ca!knight
From: knight@mrco.carleton.ca (Alan Knight)
Subject: Re: Java is not competition-Go VWave!
X-Nntp-Posting-Host: tina.mrco.carleton.ca
Message-ID: <knight.820518153@tina.mrco.carleton.ca>
Sender: news@cunews.carleton.ca (News Administrator)
Reply-To: knight@mrco.carleton.ca (Alan Knight)
Organization: The Object People
References: <4c108v$bqa$2@mhafm.production.compuserve.com> <4c1mk4$k3@sundog.tiac.net> <knight.820278646@tina.mrco.carleton.ca> <4c94sc$plb@sundog.tiac.net>
Date: Mon, 1 Jan 1996 17:42:33 GMT
Lines: 47

In <4c94sc$plb@sundog.tiac.net> kinsella@tiac.net (Joe Kinsella) writes:

>My concern would be that each time a user clicks on the Register
>button in the HTML page, my Web server will start the VW runtime, load
>a ST image, and then execute the application to verify their
>registration and add them to the database.  If I have multiple users
>registering at once, I will have multiple copies of the runtime and
>image loaded.  This would be fine if not for the siginificant overhead
>of the runtime and base image.

Yes, that would not be a particularly good way to run it. It would be
rather like saying "OK, start the database server, retrieve the
information for the web page, now shut down. Now look, the user
clicked on a button, start up the database server again to register
them, then shut it down.". VisualWave expects to run as a server, i.e.
it runs continuously and all you're doing is sending a message to it
when the user clicks on the button.  There is only one image (or at
least there doesn't have to be more than one) regardless of how many
users there are.  VisualWae also has the concept of a session, which
makes it easier to keep track of the state of different user
interactions.






>>What it has to do with Java is that it supports various browser
>>features, one of which is Java. That is, if you detect that your
>>client is using a Java-capable browser, you can have Java applets as
>>part of your application.

>This has nothing to do with VisualWave, though.  Isn't it your Web
>browser that is running Java.  If I write my CGI apps in Perl or C++,
>they too can "take advantage" of Java.  Hey, any CGI language can
>"take advantage" of Java!  Fortunately Sun, Netscape, SpyGlass,
>etc..., took the time to write this code.

This is entirely true. VisualWave is already aware of Java, which
probably makes it slightly easier to integrate, but other than that
there is no difference.
-- 
 Alan Knight                | The Object People
 knight@acm.org             | Smalltalk and OO Training and Consulting
 alan@objectpeople.on.ca    | 509-885 Meadowlands Dr.
 +1 613 225 8812            | Ottawa, Canada, K2C 3N2

