[Seaside-dev] Issue 320 in seaside: WAMutex portability

[codesite-noreply at google.com]

Updates:
	Summary: WAMutex portability
	Status: Started
	Owner: jfitzell

Comment #1 on issue 320 by jfitzell: WAMutex portability
http://code.google.com/p/seaside/issues/detail?id=320

I moved the code into WAMutex.

I also pulled the platform method right up to Platform so that is no longer  
an issue.

I'm still not sure whether we should add #activeProcess to platform... it  
seems to be
implemented the same way in GS, VW, and Squeak so it seems it may not be  
required. I
don't know about other platforms, though, and arguably it's clearer to put  
all
process methods on the platform for consistency. They can, of would, of  
course have
default implementations that would prevent most platforms from needing to  
implement them.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings