[Seaside] Re: serving files from seaside

[Jay Hardesty]

Thanks - yes I did see that error - now everything seems
fine, using a single port.

I had a problem in the form of  walkbacks when
#addCookies: was being called on an HttpRequest.  Then
I found that "HttpResponse current" had somehow
been set to an HttpRequest (instead of an HttpResponse).
Clearing out "Bindings" fixed the problem.

Now everything seems to work.

Thanks again,
Jay


On Mar 21, 2006, at 1:59 AM, Yanni Chiu wrote:

> Jay Hardesty wrote:
>> THANK YOU - yes - now even I understand, and it works.
>> Thanks for pinpointing the (current) operative gap in my
>> understanding - this eradicates a real frustration.
>
> Here's another snippet from a previous post:
>    ...
>    Before you run the code above, make sure you stop WAKom and remove
>    it from the startup/shutdown list, otherwise you'll get walkbacks,
>    or complaints that port is already used. Some code:
>
> WAKom stop
> Smalltalk removeFromStartUpList: WAKom.
> Smalltalk removeFromShutDownList: WAKom.
>
> Since you've started WAKom in two different ways,
> you may run into the same problem I did.
> You'd see the problem whenever you save image,
> or on restarting the image. But, you probably won't
> see the problem if you keep using two different
> ports (8080 & 9090).
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside