[Glass] DependentsFields and multiple gems...

Mariano Martinez Peck marianopeck at gmail.com
Thu Feb 27 14:26:43 PST 2014

Hi guys,

After 2 hours of debugging...I found the Seaside app I am developing is
using the notification strategy of #changed:  , #update:
 , DependentsFields etc...yes...don't ask why ;) I don't know why but
somewhere inside a seaside callback I have this kind of communication.

I had a very strange problem. This callback was working perfectly in Pharo.
Was working correctly in GemStone with a single Swazzo adaptor. I was
working correctly even using WAGemStoneRunSeasideGems with a single Swazzo.
However....I discovered that when using multiple FastCGI adaptors (gems) it
failed. So ... basically, if I only start one FastCGI and I define 1
upstream in the webserver, no problem it works. However....if more then 1
upsteam is alive...it doesn't work.

I *think *it could be related to the DependentsFields class var and the
lack of synchronization of it. Besides trying to use another notification
scheme....does this sound like the problem? should I do something with the
class var? (same as GLASS do for seaside class vars)

Any help is appreciated.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20140227/7218f1f5/attachment.html>

More information about the Glass mailing list