(newbee) Squeak servlets?

James Robertson jarober at gmail.com
Thu Oct 6 21:54:39 UTC 2005


Using the VW framework, you can define a servlet endpoint in an html page 
in the same way you would for a Java servlet.

What's the difference?  The image fires up a new instance instead of 
loading (and caching) from disk.  So what?



At 05:48 PM 10/6/2005, you wrote:
>On Thu, 06 Oct 2005 13:41:16 -0700, James Robertson <jarober at gmail.com>
>wrote:
>
>>Well, VW supports servlets.
>
>Terminology. If I write a CGI script, is that a servlet? No. If I write a
>little program to manage state from those CGI scripts, is THAT a servlet?
><shrug> I probably wouldn't call it that: I'd call it a server, since it
>serves the webserver.
>
>I think of a servlet as something that rests on a framework of an existing
>web server, like Tomcat. (In one sense you could look at all Smalltalk
>programs as "servlets" but that's not really useful. :-))
>
>>They don't load into a JVM like Java servlets do, but they operate the
>>same way.  You have a persistent image that keeps running, and either a
>>port redirection or CGI relay from the http server.
>>
>>In terms of how it looks at the front end, it's all just servlets - I
>>have a servlet in my blog server that implement the server side of the
>>MetaWebLog API, for instance.
>>
>>There's no reason you couldn't do the same in Squeak
>
>I believe that is what Seaside does.

<Talk Small and Carry a Big Class Library>
James Robertson, Product Manager, Cincom Smalltalk
http://www.cincomsmalltalk.com/blog/blogView




More information about the Squeak-dev mailing list