[Seaside] [ANN] Seaside 3.0.7 release
nick.ager at gmail.com
Wed Apr 4 08:37:58 UTC 2012
Could you simply update #stable version
in ConfigurationOfZincHTTPComponents to reflect your recent changes. Then I
think ConfigurationOfSeaside30 should load the correct version. Of course
the one-click and developer builds will still need to updated
On 4 April 2012 09:07, Sven Van Caekenberghe <sven at beta9.be> wrote:
> On 04 Apr 2012, at 08:52, Nick Ager wrote:
> > Hi Sven,
> > ---
> > Name: Zinc-HTTP-SvenVanCaekenberghe.248
> > Author: SvenVanCaekenberghe
> > Time: 4 March 2012, 8:25:19 pm
> > UUID: aaab5645-ed48-4174-bdb5-53037fb297db
> > Ancestors: Zinc-HTTP-SvenVanCaekenberghe.247
> > Switched ZnServer class>>#defaultServerClass to
> > […]
> > ---
> > ZnManagingMultiThreadedServer differs from its superclass
> ZnMultiThreadedServer in that it keeps explicit track of each (kept-alive)
> client connection. Tracking open client connections is important to
> correctly handle the case where people save an image with a running server.
> Before, that sometimes resulted in crashes of all kinds because even though
> the server (socket) itself came back up correctly, it happened that client
> worker process kept reading or writing to (now) stale socket streams. Now,
> when the server shuts down (#stop's) it closes all client connections
> > Currently the 3.0.7 one-click and developer images use
> ZnMultiThreadedServer rather than ZnManagingMultiThreadedServer and
> ConfigurationOfSeaside30 loads the stable configuration of Zinc which
> doesn't incorporate the change to #defaultServerClass to move from
> ZnMultiThreadedServer to ZnManagingMultiThreadedServer.
> > From your description above it sounds as though images uses
> ZnMultiThreadedServer could experience crashes. Is is worth updating the
> #stable version in ConfigurationOfZincHTTPComponents and the 3.0.7
> one-click and developer images as Zinc is now used as the default server
> > Cheers
> > Nick
> Thanks a lot for taking care and pushing this.
> Yes it would be a good idea to use a later version with the new default.
> Pharo 1.3/1/4 need another Zn update as well (the latest integrated
> version was Zinc-HTTP-SvenVanCaekenberghe.242). I will create a new issue
> for that.
> It is (and has been) possible to explicitely use
> ZnManagingMultiThreadedServer, like this:
> ZnZincServerAdaptor new
> port: 8080;
> serverClass: ZnManagingMultiThreadedServer;
> Or we could change ZnZincServerAdaptor to use that class by default.
> I would prefer the full Zn update, I guess, but that is the most work.
> Sven Van Caekenberghe
> Smalltalk is the Red Pill
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside