[Seaside] SeasideTesting

[goran.krampe at bluefish.se]

Hi David, Brent and all!

David Shaffer <cdshaffer at acm.org> wrote:
> Colin Putney wrote:
> 
> > Hi all,
> >
> > I'm trying to get set up to do some work in Seaside, and I can't seem 
> > to get SeasideTesting working. I've tried it with the current releases 
> > of both Swazoo and Comanche, but in both cases SCBrowserSimulator 
> > fails with silly errors that look more like misconfiguration than bugs.
> >
> > If SeasideTesting has suffered bit rot in the last few months I'll be 
> > happy to update it, but I don't want to go charging off in the wrong 
> > direction. Can someone point me to a known-good configuration?
> >
> 
> Hey Colin,
> 
> There is a problem with the newest Kom release.  The patch is attached.  
> I submitted a patch to Goran (maybe he has me on a kill list, he hasn't 
> responded to any of my recent e-mails).  If this doesn't solve your 
> problem, let me know off list and we can sort it out.

Eh... I did get *one* personal email with this issue mentioned on the
17th december (was on holiday then, or very soon after at least) and
have indeed missed to reply to it - too much to do simply and it slipped
through the cracks.

But I can't see that I have gotten more than one personal email. And no
- I don't use kill lists.

Anyway, after investigating this further the checks with "respondsTo:
#socket" were actually available in 6.2 (also in methods #localPort and
#localAddress) but evidently got removed by Brent Pinkney when he
refactored 6.2 quite a bit - which was the basis for 7.0.

So... this all boils down to Brent presuming that it will always be a
SocketStream held in instvar "stream" and now, with your stuff... that
isn't true. Checking with respondsTo: is ugly so I understand Brent
cleaning it away, but perhaps a bit different refactoring might be in
order so that HttpRequest can be "stream agnostic". :)

regards, Göran