Hi,
Today I was playing with the published version of Seaside made by Avi Bryant the last week, which uses the Swazoo version for Dolphin made by Sean Malloy, to add some missing functionalities I had working in my earlier port of Seaside to Dolphin.
Considering to what Sean says in his website, the port is based on the 0.9.101 version, while Steve Waring's one is based on 0.9.99 (apparently). Sean's version is more conscise in terms of number of packages, but it misses some classes such as SwazooSiteScript and other very useful tools, available in Steve's version.
Considering that the Swazoo topic got warm this days, and that today it's more a jungle than a zoo ;-), we could arrange some efforts to make it converge into a single stream of development, at least compatible with what already exists in Dolphin.
For example, you can't have Seaside and Spray web services running on the same image, because they're incompatible (besides the fact that the naming convention of Steve is different to the Sean's one*).
Plus, Dolphin ships with Steve's version, which is appropriate considering the existing goodies and packages available, but not the best option aiming to a broader audience through Seaside and other popular developments that would come.
I leave the topic here, to see if there is enough interest to make it happen. I would like to see Sean, Steve, Janko, the OA people, perhaps Bruce Badger too, and anybody willing to collaborate at least in testing, joining efforts for this.
Best regards,
-- Esteban.
* Steve: I will be happy to know what SW, SV, and other prefixes mean. :-)
ps: this is a cross-post to c.l.s.d, Swazoo and Seaside mailing lists, sorry for any inconvenience caused.
I'm interested. I'll do what I can.
regards,
Sebastian
-----Mensaje original----- De: seaside-bounces@lists.squeakfoundation.org [mailto:seaside-bounces@lists.squeakfoundation.org] En nombre de Esteban A. Maringolo Enviado el: Domingo, 28 de Mayo de 2006 21:12 CC: Seaside Mailing List; Swazoo List Asunto: [Seaside] Swazoo versions
Hi,
Today I was playing with the published version of Seaside made by Avi Bryant the last week, which uses the Swazoo version for Dolphin made by Sean Malloy, to add some missing functionalities I had working in my earlier port of Seaside to Dolphin.
Considering to what Sean says in his website, the port is based on the 0.9.101 version, while Steve Waring's one is based on 0.9.99 (apparently). Sean's version is more conscise in terms of number of packages, but it misses some classes such as SwazooSiteScript and other very useful tools, available in Steve's version.
Considering that the Swazoo topic got warm this days, and that today it's more a jungle than a zoo ;-), we could arrange some efforts to make it converge into a single stream of development, at least compatible with what already exists in Dolphin.
For example, you can't have Seaside and Spray web services running on the same image, because they're incompatible (besides the fact that the naming convention of Steve is different to the Sean's one*).
Plus, Dolphin ships with Steve's version, which is appropriate considering the existing goodies and packages available, but not the best option aiming to a broader audience through Seaside and other popular developments that would come.
I leave the topic here, to see if there is enough interest to make it happen. I would like to see Sean, Steve, Janko, the OA people, perhaps Bruce Badger too, and anybody willing to collaborate at least in testing, joining efforts for this.
Best regards,
-- Esteban.
- Steve: I will be happy to know what SW, SV, and other
prefixes mean. :-)
ps: this is a cross-post to c.l.s.d, Swazoo and Seaside mailing lists, sorry for any inconvenience caused.
Seaside mailing list Seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
I agree that it would be good to converge the multiple versions of Swazoo. With Janko now using Dolphin, that should be easier. A Dolphin port of Sport would also be handy. Unfortunately I don't have the time to work on it, but I would be happy to help, test etc.
Some thoughts:
- I think it would be better to see a definite resolution of the Hyper/Swazoo split before bringing the old Dolphin version up to the latest version.
- Personally I do see Swazoo as being fairly modular ... the two main modules being the http server and the resource framework. In the past, I have plugged CGI servers and FastCGI servers into the Swazoo resource framework, and also used the Swazoo http server with different content systems.
It sounds like Avi has taken the latter approach with Seaside-Dolphin. With the original Seaside-Dolphin port, I did use the Swazoo resource framework via #resolveNamespaceResource: ... but the concept of namespace resources may not be a part of the latest Swazoo versions.
- Steve: I will be happy to know what SW, SV,
and other prefixes mean. :-)
I use SV for packages that contain servers that can be deployed as executables (both Swazoo based and CGI/FastCGI based).
I use SW as a kind of default namespace, both for packages and classes.
FWIW: When I extended the Dolphin port (from Jerry Bell's original work), I was a touch naive and a bit too keen. If I had been a bit more restrained, or if I had tried harder to get the changes folded back into the VW version, some of this mess would not exist. Live and learn!
Steve
ps: this is a cross-post to c.l.s.d, Swazoo and Seaside mailing lists, sorry for any inconvenience caused.
Ditto.
Hi Esteban and others!
For start I prepared a table of Swazoo versions for all supported dialects at: http://www.swazoo.org/download.html. It is not yet complete and I hope someone will help me with some more info.
I also opened a FTP server at ftp://www.swazoo.org/swazoo , where IMO we should put all those versions to be on one place.
Best regards Janko
Esteban A. Maringolo wrote:
Hi,
Today I was playing with the published version of Seaside made by Avi Bryant the last week, which uses the Swazoo version for Dolphin made by Sean Malloy, to add some missing functionalities I had working in my earlier port of Seaside to Dolphin.
Considering to what Sean says in his website, the port is based on the 0.9.101 version, while Steve Waring's one is based on 0.9.99 (apparently). Sean's version is more conscise in terms of number of packages, but it misses some classes such as SwazooSiteScript and other very useful tools, available in Steve's version.
Considering that the Swazoo topic got warm this days, and that today it's more a jungle than a zoo ;-), we could arrange some efforts to make it converge into a single stream of development, at least compatible with what already exists in Dolphin.
For example, you can't have Seaside and Spray web services running on the same image, because they're incompatible (besides the fact that the naming convention of Steve is different to the Sean's one*).
Plus, Dolphin ships with Steve's version, which is appropriate considering the existing goodies and packages available, but not the best option aiming to a broader audience through Seaside and other popular developments that would come.
I leave the topic here, to see if there is enough interest to make it happen. I would like to see Sean, Steve, Janko, the OA people, perhaps Bruce Badger too, and anybody willing to collaborate at least in testing, joining efforts for this.
Best regards,
-- Esteban.
- Steve: I will be happy to know what SW, SV, and other prefixes mean. :-)
ps: this is a cross-post to c.l.s.d, Swazoo and Seaside mailing lists, sorry for any inconvenience caused.
Hi Janko,
Just a quick question. I tried utf-8 in the content-type but no encoding seems to be performed. Does Swazoo encode the HTTP response or is it the responsibility of the application ?
Thanks, Michel.
Here's how I hacked my Seaside/Swazoo to serve UTF8; its nasty but seems to work. I wouldn't mind something cleaner though, so feedback from Janko would still be greatly appreciated.
WAResponse>>initialize ... stream := EncodedStream on: (ReadWriteStream on: (ByteArray new: 5000)) encodedBy: (StreamEncoder new: #'utf-8'). ...
SeasideResource>>convertResponse: ... swazooResponse entity: ((waResponse contents class = EncodedStream) ifTrue: [waResponse contents stream contents] ifFalse: [waResponse contents contents]). ...
Cheers!
-Boris
Hi Esteban and others,
Esteban A. Maringolo wrote:
For example, you can't have Seaside and Spray web services running on the same image, because they're incompatible (besides the fact that the naming convention of Steve is different to the Sean's one*).
Plus, Dolphin ships with Steve's version, which is appropriate considering the existing goodies and packages available, but not the best option aiming to a broader audience through Seaside and other popular developments that would come.
I leave the topic here, to see if there is enough interest to make it happen. I would like to see Sean, Steve, Janko, the OA people, perhaps Bruce Badger too, and anybody willing to collaborate at least in testing, joining efforts for this.
For Dolphin I propose the next plan:
1. Port SPort portability layer to Dolphin (urgent!), 2. port Swazoo 1.1.x (dev.branch towards 2.0) to Dolphin, 3. adjust Seaside and Aida to a new Swazoo, 4. include changes and goodies (like GUI console) from Steve's Swazoo, 5. release Swazoo 2.0 on Dolphin, together with 2.0 on other dialects.
In parallel there would be nice to do the same for Squeak and maybe some other dialect too, so that we can exchange porting experiences and also make Swazoo even more easy to port in future.
See also my statement of direction at http://www.swazoo.org/development.html
So, all that said I think we can achieve as you propose, Esteban. But porting SPort is definitively a first step. Is there anyone who is willing to do SPort port ASAP?
Best regards Janko
seaside@lists.squeakfoundation.org
-
Boris Popov -
Esteban A. Maringolo -
Janko Mivsek -
Michel Bany -
Sebastián Sastre -
Steve Waring