Re: Swazoo troubles and enhancements suggestions

> Hello Janko,
>
> I looked at v0.9.90 and was pleased to see that
> many (well most) of the issues I had are resolved :
>
> 1.1. File name in MIME entity.
> I could see that this is now handled by v0.9.90
> although I personally would have placed the filename i-var
> in the superclass MimeObject.
>
> 2.2 WSAEINVAL when executing SwazooServer configureFrom: 'sites.cnf'
> Does not occur with v0.9.90
>
> 2.3 Redirection (code 302)
> Works fine with v0.9.90 for both IE6 and Mozilla
>
> I do not know how to post on Swazoo mailing list.
> I already informed Bruce Badger about my issues.
> He may have worked on them.
>
> The rest was only suggestions from myself
> that help Seaside in Swazoo :
> 1.2. Seaside needs the actual HTTP method value,
> See package Swazoo/Patches on store.
> 1.3. Configuring Swazoo from any stream,
> See package Swazoo-LoadFromBundle
> 1.4. Time zones and GMT,
> This is needed for proper expiration of pages
> and cookies. See package Swazoo/Patches on store.
> 2.1. Manipulating cookies,
> See package Swazoo/Patches on store.
>
> Feel free to roll-in any of my suggestions
> into Swazoo 1.0.
>
> Please note.
> 1. If you want to have a look at the Seaside
> stuff, load bundle named SeasideForSwazoo. This
> automatically loads all the pieces in the correct
> order.
> 2. SeasideForSwazoo will be placed on the next VW
> distribution CD.
>
> Kindest regards,
> Michel.
>
>
>  > -----Original Message-----
>  > From: Janko Mivšek [mailto:[hidden email]]
>  > Sent: Friday, October 22, 2004 10:29 PM
>  > To: Bany, Michel
>  > Subject: Re: Swazoo troubles and enhancements suggestions
>  >
>  >
>  > Hi Bany,
>  >
>  > Your mail was declared as spam by my Mozilla but fortunately i saw it
>  > soon enough :)
>  >
>  > I'll respond to your questions in monday, in the meantime look at
>  > v0.9.90 from Cincom Store. Also, put next questions on
>  > mailing list so
>  > that Bruce Badger as currently most active Swazooer can help too.
>  > Anyway, we are preparing a version 1.0, so your questions
>  > arived just at
>  > the right time ;)
>  >
>  > Have a nice weekend
>  > Janko
>  >
>  >
>  > Bany, Michel wrote:
>  > > Hello Janko,
>  > >
>  > > I am nearly done with hooking Seaside-VW to Swazoo,
>  > > and I am getting some trouble.
>  > > Since it looks as if you became the main maintainer
>  > > of Swazoo, I am coming to you, hoping you will be
>  > > able to help me.
>  > >
>  > > I am using Swazoo from the public store.
>  > >
>  > > You can have a look to my work on the Cincom
>  > > public store, bundle SeasideForSwazoo.
>  > > This will be on the next VW distribution.
>  > >
>  > > May I first suggest some enhancements to Swazoo,
>  > > then request your help with my difficulties.
>  > >
>  > > 1. Suggestions.
>  > >
>  > > 1.1. Seaside needs the file name when a MIME
>  > > entity is part of the HTTP request. However this
>  > > piece of data is not extracted from the request
>  > > and not passed along to the post data.
>  > > My suggestion :
>  > > a) add an instance variable "filename" to
>  > > Swazoo.MimeObject with accessors.
>  > > b) extract the filename from the HTTP request
>  > > in HTTPPost>>partFromBytes: using this fragment
>  > > of code
>  > >         ...
>  > >         field isContentDisposition ifTrue:
>  > >                 [(field parameterAt: 'filename') notNil ifTrue:
>  > >                         [datum filename: ((field parameterAt:
>  > > 'filename') copyWithout: $")].                                  
>  > >              
>  > >
>  > >                 name := (field parameterAt: 'name')
>  > copyWithout: $"].
>  > >         ...
>  > >
>  > > 1.2. Seaside needs the actual HTTP method value,
>  > > i.e. 'GET', 'POST', etc for testing a request.
>  > > Therefore I suggest that HTTPRequest implements
>  > > #method where concrete subclasses answer the
>  > > appropriate constant.
>  > >
>  > > 1.3. I suggest also that SwazooServer>>configureFrom:
>  > > is re-factored so that you can configure Swazoo
>  > > from any stream, not necessarily a file.
>  > >
>  > > 1.4. You may be interested in some patches I created
>  > > for Swazoo that you will find in my SeasideForSwazoo
>  > > bundle. For instance, I believe I have solutions for
>  > > the time zone issues.
>  > >
>  > > 2. Questions & difficulties
>  > >
>  > > 2.1. I borrowed some code from the Web Toolkit to
>  > > manipulate cookies because it looks as if there is
>  > > no explicit support for cookies in Swazoo. Do you
>  > > confirm my finding ?
>  > > If yes you may want to roll-in the cookies support
>  > > stuff from the SeasideForSwazoo into the Swazoo
>  > > bundle. Then I will be able to take away from my
>  > > bundle. What do you think ?
>  > >
>  > > 2.2 I configure the SwazooServer with 'sites.cnf'
>  > > as shown below
>  > >
>  > > <Site>
>  > >  <SiteIdentifier ip: '127.0.0.1' port: 8888 host: 'localhost' >
>  > >
>  > >  <CompositeResource uriPattern: '/'>
>  > >   <CompositeResource uriPattern: 'foo'>
>  > >    <HelloWorldResource uriPattern: 'Howdy'>
>  > >   </CompositeResource>
>  > >  </CompositeResource>
>  > >
>  > >  <FileResource uriPattern: '/' filePath: '.'>
>  > >
>  > >  <CompositeResource uriPattern: '/'>
>  > >   <SeasideResource uriPattern: 'seaside'>
>  > >  </CompositeResource>
>  > > </Site>
>  > >
>  > > When executing SwazooServer configureFrom: 'sites.cnf',
>  > > I am getting a WSAEINVAL exception, i.e. error code 10022
>  > > in the SocketAccessor, see the attachement. When proceeding,
>  > > everything works fine though.
>  > >
>  > > 2.3 Seaside always use redirection (code 302). This
>  > > works fine with Mozilla 1.7, but does not work with IE6.
>  > > I created a non-Seaside Swazoo resource  with the
>  > > following logic
>  > >         answerTo: aRequest
>  > >                 | response |
>  > >                 response := HTTPResponse redirectLink.
>  > >                 response addHeaderName: 'Location' value:
>  > '/foo/Howdy'.
>  > >                 response
>  > >                         contentType: 'text/html';
>  > >                         entity:
>  > >
>  > '<html><head><title>Redirect</title></head><body>Redirect</bod
>  > y></html>'.
>  > >                 ^response
>  > > This works fine under Mozilla and fails with IE6.
>  > > I had the idea to use HTTPLook, an HTTP sniffer
>  > > from http://www.httpsniffer.com/index.htm When
>  > > HTTPLook is running, capturing HTTP traffic,
>  > > the IE6 failure does not happen !!!
>  > >
>  > > Hoping you can help me,
>  > > Michel.
>  > >
>  > >
>  > > _________________________________
>  > > Michel Bany
>  > > Cincom Systems S.A.
>  > > Avenue Louis Casaï 18
>  > > 1211 GENEVE 28
>  > > Switzerland
>  > > Phone : +41 22 747 75 18
>  > > Mobile : +33 608 933 306
>  > > Fax : +41 22 747 79 90
>  > > Email : [hidden email]
>  > > Home page : www.cincom.com/smalltalk/
>  > >
>  > >