3.7/3.8 FileStream compatibility and Seaside/KomHttpServer

Brent Pinkney brent.pinkney at aircom.co.za
Sun Mar 6 17:17:05 UTC 2005


> In my working 3.7 image a StandardFileStream instance is constructed when
> FileDirectory is asked for the
> read only file. In the predefined seaside image a MutiByteFileStream is
> constructed. The reason is the
> implementation of FileStream(class)>>concreteStream which returns
> StandardFileStream (3.7) or
> MutiByteFileStream (3.8). The 3.8 implementation is from "yo" (7/5/2004).
>
> I could easily fix the seaside image by changing
> FileStream(class)>>concreteStream to return a
> StandardFileStream again - but I don't know about the side effects this  
> will
> have in the 3.8 image.
>
> Question left is how we can handle the 3.7/3.8 differences in
> Seaside/KomHttp and other applications.
>
> Any comments?

I identified this bug back in January 2005. I made the same change you did.

Ned or Tim (?) mentioned that they had some previous comments on this to  
the effect that the calling code should instruct the file to open in  
binary mode.

I do not know enough about this to comment more.

Brent



More information about the Squeak-dev mailing list