VLib Synchronisation issue tap4

[Numa Schmeder <nu...@euroconsumers.com>]

Hello,

Maybe someone can explain me something.  In Tapestry 4 VLib example  
the BookQuerySource implementation has some of its methods  
synchronised.  I don't understand why?  Shouldn't it be unnecessary  
as the hivemind service is set to threaded.  I thought a threaded  
service would be only available for the current thread and not shared  
with other threads, so why synchronize some methods?
Could someone explain me this issue?  The same is going on for  
ModelSource !
Help would be greatly appreciated.

Numa


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org