Hello all, Have there been any changes to the way Seaside behaves? I recall two things: (1) using it caused my image to bloat up by an additional 30+MB; (2) I could safely use #startOn: and #stop to control whether or not it was running.
Now I am finding the bloat is not nearly so bad as before[*], and every image save seems to restart the Seaside process, whether I had used #stop or not. A side effect of the latter is that #startOn: ends up complaining about a service already being on 8080 (and the process is running), even though WAKom port returns nil. I, rather un-deftly, tweaked the way I register my Seaside apps, so I'm willing to entertain the idea that I confused something. Bottom line: have there been any relevant changes to expected behavior, and if not, any thoughts on how to undo any confusion I might have caused? Bill [*] Perhaps I am stumbling less with time, maybe leaving a reduced amount of challenging junk for the GC?? _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
