[Seaside] Scamper vs. non-Squeak browser

Avi Bryant avi at beta4.com
Mon May 12 21:00:58 CEST 2003


On Mon, 12 May 2003, Jim Menard wrote:

> When I try to use Seaside from within Scamper, it displays the error
> message
>
> 	error occured retrieving http://localhost:9090/seaside/rate: Could not
> resolve the server named:

I played around with this a bit, and the problem is definitely with
Scamper - or rather, with the HTTPSocket class that it uses.  This is a
really fragile HTTP client, as I've found when trying to use it before -
in this case, it's not properly supporting relative paths in redirects.
That particular problem looks like it can be fixed by changing the '../'
string literal in HTTPSocket class>>expandUrl:ip:port: to '/' instead (I'm
completely perplexed by the use of '../' in this method), but after doing
this I immediately ran into another problem, that seems like it might be
related to Scamper mistreating the '@' sign in Seaside urls.  It's
possible that someone could also fix this one fairly easily, but in
general I'm not optimistic about Scamper being useful for Seaside work
until someone revamps the HTTP client implementation (which I understand
Stephen is trying to lay some groundwork for anyway).

Avi



More information about the Seaside mailing list