[Seaside-dev] any porters need anything else for a beta?

[Dale Henrichs]

I'm just now working through some concurrency issues related to WACache so I'm not quite done. I should be finished with those those issues within the week.

I've been making changes to a couple of the packages using GemStone branches (Seaside-Core and Seaside-Session) that are related to needing to use GemStone-specific classes instead of the Seaside defaults. It also looks like I'll be changing the default error handler and WARegistry class>>clearAll uses allInstances which is causing problems for GemStone - I'm thinking of writing something to traverse the applications reachable from the default dispatcher which should be applicable as a general solution (looking at things, it might be necessary to reorder the calls in WAEnvironment class>>reloadApplications, but I haven't got into it too deep).

It would be nice to make those places pluggable, but I would like to get through the WACache issues then we can take a look at whether Grease methods or another technique or GemStone-branch would be the best solutions.
 
Dale

----- "Julian Fitzell" <jfitzell at gmail.com> wrote:

| Dale, I'm looking mostly at you since you've been actively working on
| your port. We should try to get a beta out Real Soon Now. Are you
| done
| the changes you need?
| 
| Julian
| _______________________________________________
| seaside-dev mailing list
| seaside-dev at lists.squeakfoundation.org
| http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev