Hello, I'm enquiring as to whether anyone has done any work running Squeak rather than a servlet (or even JSPs) on a servlet engine with Apache and DB or if not, can anyone give me some relevant info such as different methods to achieve the same end.
There's a few things I'd like to do in that vein and servlets is the only way I know how (not knowing perl or php) but I'd be more interested in using Squeak if possible.
I should also mention that I'll be using a free host with apache.
Thanks! Gary
The code for doing servlets in VisualWorks Smalltalk is already out there. Have a look at WhiteCap (http://www.jdmsoft.com/WhiteCap.html), which implements the Java Servlet Specification version 2.2. This is for VW, not Squeak, but I'm sure it could be ported.
Perhaps you could try it using the non-commercial version of VisualWorks to see if it's what you want before porting it to Squeak, although having a Squeak port would be useful as well. :)
Aaron
Gary McGovern garywork@lineone.net said:
I'm enquiring as to whether anyone has done any work running Squeak = rather than a servlet (or even JSPs) on a servlet engine with Apache and = DB or if not, can anyone give me some relevant info such as different = methods to achieve the same end.
It's still not completely complete, but you can find a lot of stuff to help Squeak on the Net in Comanche. Servlets are the basic and standard way any object system will want to publish to the net, so even if Comanche doesn't follow any standards, it's quite accessible. The equivalent of JSP is SSP, implemented by Stephen Pair for Squeak - it should be part of Comanche by now or at the very least quickly become part of it (there were some interoperability problems).
The biggest thing missing is the possibility to put Squeak behind a Webserver via a custom CGI script or - better - something like FCGI. VisualWorks has this in the upcoming release, and especially FCGI with 'auto-start' (I think that's part of the FCGI spec - what I mean is that on the first FCGI request, the CGI script starts the server if it's not already running) would be a nice way to deploy Smalltalk with any Apache hoster.
Squeak has drivers for PostgreSQL and mySQL, and possibly some more.
"Cees de Groot" wrote:
It's still not completely complete, but you can find a lot of stuff to
help
Squeak on the Net in Comanche. Servlets are the basic and standard way any object system will want to publish to the net, so even if Comanche doesn't follow any standards, it's quite accessible. The equivalent of JSP is SSP, implemented by Stephen Pair for Squeak - it should be part of Comanche by
now
or at the very least quickly become part of it (there were some interoperability problems).
That's interesting. Would I be right in thinking there are two separate and distinct comanchies ? I just installed comanche today with apache but it didn't seem to have any relevance to Squeak. But it was a version over a year old.
The biggest thing missing is the possibility to put Squeak behind a Webserver via a custom CGI script or - better - something like FCGI. VisualWorks has this in the upcoming release, and especially FCGI with 'auto-start' (I think that's part of the FCGI spec - what I mean is that on the first FCGI request, the CGI script starts the server if it's not already running) would be a nice way to deploy Smalltalk with any Apache hoster.
Do you know of any work being done on this ? I like to think of Squeak as an environment of plasticity (ie to shape to any task), do you think that goes against the grain of most work being done?
Squeak has drivers for PostgreSQL and mySQL, and possibly some more.
I was aware of that. Thanks!
Aaron wrote: The code for doing servlets in VisualWorks Smalltalk is >already out there. Have a look at WhiteCap >>>(http://www.jdmsoft.com/WhiteCap.html), which implements the Java Servlet Specification version 2.2. >This is for VW, not Squeak, but I'm sure it could be ported.
Thanks for this. I'm not so sure that 'ported' would be the correct term for this.:-) But I'm sure some things may filter through, though I wouldn't want to do that. I never realised that VW had already done it, I thought it was coming soon.
Delbert Murphy wrote: You can write a Module for Comanche or add to Swiki >+ Comanche.
I believe that this is a good place to start: http://minnow.cc.gatech.edu/swiki
Thanks for the pointers.
Regards, Gary
"Gary McGovern" garywork@lineone.net wrote:
"Cees de Groot" wrote:
It's still not completely complete, but you can find a lot of stuff to
help
Squeak on the Net in Comanche. Servlets are the basic and standard way any object system will want to publish to the net, so even if Comanche doesn't follow any standards, it's quite accessible. The equivalent of JSP is SSP, implemented by Stephen Pair for Squeak - it should be part of Comanche by
now
or at the very least quickly become part of it (there were some interoperability problems).
That's interesting. Would I be right in thinking there are two separate and distinct comanchies ? I just installed comanche today with apache but it didn't seem to have any relevance to Squeak. But it was a version over a year old.
The biggest thing missing is the possibility to put Squeak behind a Webserver via a custom CGI script or - better - something like FCGI. VisualWorks has this in the upcoming release, and especially FCGI with 'auto-start' (I think that's part of the FCGI spec - what I mean is that on the first FCGI request, the CGI script starts the server if it's not already running) would be a nice way to deploy Smalltalk with any Apache hoster.
Do you know of any work being done on this ? I like to think of Squeak as an environment of plasticity (ie to shape to any task), do you think that goes against the grain of most work being done?
It does go against the grain: the mechanisms are particular to individual platforms! On one platform FCGI talks over stdin/stdout, and on another it talks over a loopback socket, and on others it can be implemented in still other ways. The only IPC mechanism available everywhere is TCP/IP, and that's what Comanche uses by default.
If platform specificity is okay with you, then FCGI sounds like a fine way to hook Squeak to Apache. Check out OSProcess to get started, so that you can actually talk to stdin and stdout.
-Lex
Thank you Lex for this email and the previous. There seems a lot there and I'll probably need to see what I can do on localhost and then take it from there.
Regards, Gary
----- Original Message ----- From: "Lex Spoon" lex@cc.gatech.edu To: squeak-dev@lists.squeakfoundation.org Sent: Tuesday, July 31, 2001 10:15 PM Subject: Re: Squeak instead of Servlets
"Gary McGovern" garywork@lineone.net wrote:
"Cees de Groot" wrote:
It's still not completely complete, but you can find a lot of stuff to
help
Squeak on the Net in Comanche. Servlets are the basic and standard way
any
object system will want to publish to the net, so even if Comanche
doesn't
follow any standards, it's quite accessible. The equivalent of JSP is
SSP,
implemented by Stephen Pair for Squeak - it should be part of Comanche
by
now
or at the very least quickly become part of it (there were some interoperability problems).
That's interesting. Would I be right in thinking there are two separate
and
distinct comanchies ? I just installed comanche today with apache but it didn't seem to have any relevance to Squeak. But it was a version over a year old.
The biggest thing missing is the possibility to put Squeak behind a Webserver via a custom CGI script or - better - something like FCGI. VisualWorks has this in the upcoming release, and especially
FCGI
with 'auto-start' (I think that's part of the FCGI spec - what I mean is that on the first FCGI request, the CGI script starts the server if it's not already running) would be a nice way to deploy Smalltalk with any Apache hoster.
Do you know of any work being done on this ? I like to think of Squeak
as an
environment of plasticity (ie to shape to any task), do you think that
goes
against the grain of most work being done?
It does go against the grain: the mechanisms are particular to individual platforms! On one platform FCGI talks over stdin/stdout, and on another it talks over a loopback socket, and on others it can be implemented in still other ways. The only IPC mechanism available everywhere is TCP/IP, and that's what Comanche uses by default.
If platform specificity is okay with you, then FCGI sounds like a fine way to hook Squeak to Apache. Check out OSProcess to get started, so that you can actually talk to stdin and stdout.
-Lex
Hello, I'm enquiring as to whether anyone has done any work running Squeak = rather than a servlet (or even JSPs) on a servlet engine with Apache and = DB or if not, can anyone give me some relevant info such as different = methods to achieve the same end.
You can run PWS and the never Comanche as servers on their own port. I don't know of anyone who has gotten Squeak to run underneath Apache, though it's doable with a little programming.
There's a few things I'd like to do in that vein and servlets is the = only way I know how (not knowing perl or php) but I'd be more interested = in using Squeak if possible.=20
Squeak comes with PWS. With PWS, you implement one method #process: which accepts a HTTP request and puts a reply back. Hook your class up like this:
PWS link: 'testservlet' to: MyClass new
Start PWS like this:
PWS serveOnPort: 8080 loggingTo: 'pws.log'
Now you can connect to /testservlet on the localhost and it will run your #process: command. To figure out how to write #process: methods, see ScreenshotAction for a very simple example, ServerAction for a fairly simple example, and SwikiAction for a complicated example.
If you really get into it, you'll probably want to grab Comanche. I'm afraid I don't know details of getting started with Comanche, though....
-Lex
squeak-dev@lists.squeakfoundation.org