[Seaside] ProxyPass and the P Option

Boris Popov boris at deepcovelabs.com
Wed Nov 7 00:59:09 UTC 2007

That would of course depend on what the application actually does, I bet one could deploy /counter application rather quickly ;)


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 Richard Eng
> Sent: Tuesday, November 06, 2007 3:58 PM
> To: Seaside - general discussion
> Subject: Re: [Seaside] ProxyPass and the P Option
> Instead of
>     self session currentRequest cookies at: #server
> I had to do
>     self session currentRequest cookies at: #server ifAbsent:
> because #at: throws a ³key not found² exception.
> Thank you very much, Ramon! You rock!
> My web app is essentially complete now. Our website is SSL-secured. My app
> is load-balanced. Once I work out some streaming video issues, I'll be
> able
> to deploy our 1U rack server (to be colocated at a host provider).
> Then we can start our beta test program in the New Year. With any luck,
> our
> website will go live next summer. I started this Seaside project in June
> and
> within one year I expect to go live. *One year!!* Let's see a Java/Struts
> or
> PHP or C#/ASP.NET developer accomplish that!
> Regards,
> Richard
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list