[Seaside] VisualWorks + WebServers

Boris Popov boris at deepcovelabs.com
Tue Jul 24 23:48:51 UTC 2007


Thanks, that's what I wanted to hear and really can't think of anything
else I would add or change as far as your plan is concerned. While I do
agree with your hesitation with regards to Swazoo we should all keep the
"simplest thing that could possibly work" principle in mind at all times
and Swazoo, while fulfilling its role, is too much of a web server for
Seaside considering none of its other features are utilized in this

My next obvious question is, when can I take this for a test drive? ;)



DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5

boris at deepcovelabs.com


This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Michael Lucas-Smith
> Sent: Tuesday, July 24, 2007 4:42 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] VisualWorks + WebServers
> I was wondering when this topic was going to come up and how exactly
> put my 2c in. There was a sudden flourish of excitement about Swazoo
> that I didn't want to kill.
> We're making Seaside in VisualWorks run on Opentalk-HTTP. This is the
> raw streaming http server code, the most modern we have. It's fast,
> scalable, solid and comes with no bells or whistles at all. You won't
> loading in WebToolKit, TinyHttp, Swazoo or anything else, just
> Opentalk-HTTP.
> Further to this, it'll come as the default configuration. You'll be
> to continue using Swazoo or WebToolKit if you want, but if you load
> "Seaside", just like in Squeak, it'll load up fully configured with
> Opentalk-HTTP (or Komanche in Squeak) ready to run, out of the box.
> The obvious win here is that new users don't have to scratch their
> trying to figure out what package or bundle they're meant to load.
> Fixing that is goal number one. The second obvious win here is
> performance.. the Opentalk-HTTP code is very efficient - and Martin
> Kobetic is continuing to improve on that every day. The third win here
> is the streaming capabilities, which don't seem to exist in Swazoo yet
> and do exist in WebToolKit but in a weird way. It'll be nice to have
> Async, Comet and ShoreComponents, etc, simply work out of the box
> without hassle.
> For the majority of users, which HTTP server to use in VisualWorks
> now be a complete non-issue. I know this blocks out Swazoo a bit and
> sorry for that, but I have to go with the server that the consensus
> in engineering feels is the best direction to go - and that is
> Opentalk-HTTP.
> There are bigger plans afoot to move WebToolKit on to Opentalk-Wave
> which is built off Opentalk-HTTP. This would provide the basis for all
> three web frameworks in VisualWorks: Seaside, WebToolKit and
> Obvious that goal is a while off and I've got the team focusing on our
> primary framework first - Seaside.
> The actual integration with Seaside is pretty minuscule. There are a
> couple of classes and a handful of extensions. It speaks volumes for
> Seaside's HTTP interface design that it's so easy to hook up.
> Cheers,
> Michael
> Boris Popov wrote:
> > Michael,
> >
> > Since you're now the lead for Cincom's Seaside efforts I was
> > if there's any intention to be able to run Seaside behind Tiny
> > all of session/site/resource management overhead. Perhaps a glue
> > for HttpServerStreams is in order instead? I don't mind Swazoo, but
> > still seems a bit of overkill for what little is actually required
> > Seaside ;)
> >
> > Cheers!
> >
> > -Boris
> >
> >
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list