[Seaside] My progress with Seaside...
avi.bryant at gmail.com
Fri Jan 6 23:47:31 CET 2006
On Jan 5, 2006, at 10:45 AM, Avi Bryant wrote:
> On Jan 5, 2006, at 8:53 AM, Cees De Groot wrote:
>> On 1/5/06, Jeremy Shute <shutej at crazilocks.com> wrote:
>>> Which basically means I can't use Seaside any further on this
>>> project. :-(
>> .. or hope for/implement a quick chunked-transfer-encoding hack...
> ... or even do without Keep-Alive and use HTTP 1.0 streaming (there
> seem to be problems with Keep-Alive and reverse proxying anyway).
> Tell you what, I should have some time late tonight or tomorrow to
> try to hack some kind of proof of concept of a fully streaming
> Seaside, so that you can at least see if it makes a difference...
Ok, I promised a hack and a hack it is, but...
1. Make sure you have FastSocketStream loaded from SqueakMap
2. Load http://squeaksource.com/Seaside/Seaside2.6a2-avi.77.mcz
3. WAListener startOn: 8081
Now try accessing your app from 8081 instead of 8080 or whatever
usual port you use. Notes:
- This doesn't do Keep-Alive or chunked encoding; it uses HTTP 1.0,
- WAListener largely bypasses Comanche (using it only to parse the
HttpRequest), so there's much less there in terms of error handling
- It WILL NOT WORK if you use a WATask subclass
- I can't measure or perceive a performance benefit on localhost,
though I *can* see the difference if I use telnet to simulate an HTTP
request. I have yet to do any testing with remote servers.
I'm curious to see if this makes a difference for anyone.
More information about the Seaside