Re: [Wonder-disc] EOF Stack sync

[Kieran K. <kie...@ma...>]

Changed and all tests pass for ( "really only need to not set  
maxCoordinators propery at all and just call  
ERXObjectStoreCoordinatorSynchronizer.initialize() in my app  
constructor" )

Wonder never ceases to stop adding value ..... everyone should use  
the ERXObjectStoreCoordinatorSynchronizer

Now, if I need to use the Pool, I may be back with questions about  
the ERXEC factory it provides since I have my own ERXEC factory that  
makes a subclass of ERXEC.

Thanks Mike,

Regards, kieran


On Apr 20, 2007, at 8:59 AM, Kieran Kelleher wrote:

>  Looking at the Synchronizer code, it seemed apparent that it  
> subscribes to notifications for the creation and disposition of  
> OSCs, so therefore I believed it picks the creation of OSC's.  
> Logging out the optimistic locking keys before the deletes and  
> after they had been changed in another stack which I created for a  
> long task shows that indeed the attributes reflect the changes done  
> in the separate stack.
>
> So,
too early ...... I never finished this sentence ....


> On Apr 19, 2007, at 11:41 PM, Mike Schrag wrote:
>
>> I'm not sure I follow ... Why are you setting maxCoordinators to  
>> only one?
>> Presumably if you want stack sync, you want maxCoordinators > 1  
>> (i.e. more than one stack).
>
> My app works fine using one OSC for normal user (customers) load,  
> however I have certain long running (10 - 20 mins) very EOF  
> intensive tasks that are run occasionally by inhouse production/ 
> admin and these automatically create new OSC's for those tasks (If  
> I didn't, the whole app gets choked by the long running task  
> activity while they are running.
>
>
>> Or are you using synchronization without using wonder's  
>> ERXObjectStoreCoordinatorPool?
> I understood, that I need to set it to at least 1 to use any EOF  
> synchronization .... reading again as shown here (it was late last  
> night when reading it), it does say "remote", so I did not read it  
> accurately.
> ## To use remote EOF synchronization, you must turn on the
> ## ERXObjectStoreCoordinatorPool.  Just setting it to 1 is enough to
> ## allow things to work.
> #er.extensions.ERXObjectStoreCoordinatorPool.maxCoordinators=1
>
> So, really I don't need the pool (right now anyway), but I do need  
> EOF stack sync for OSC's created
>
>>  In Wonder-proper (extends ERX*), the existence of the  
>> maxCoordinators key triggers the pool and the synchronizer to  
>> automatically be initialized at startup.
>
> Ah, I did not examine the source of ERXOSCCoordPool enough to see  
> that .....
>
>
>> I guess if you're not using the pool, there's no real requirement  
>> to set maxCoordinators.
>
> Question: So, for just synchronization of OSC's that I create  
> myself, I really only need to not set maxCoordinators propery at  
> all and just call ERXObjectStoreCoordinatorSynchronizer.initialize 
> () in my app constructor to make the singleton observer, right?
>
>>
>> ms
>>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/ 
> _______________________________________________
> Wonder-disc mailing list
> Won...@li...
> https://lists.sourceforge.net/lists/listinfo/wonder-disc