Armin, Grats on your daughter! Mine is 14 now.
I trying to manage internationalization (UTF8) and a potential scaling requirement for http://www.jobbank.com which has been using OJB for years. To handle the scaling potential, I was considering either going vertical or using distributed caching. I think I have decided to go with vertical for now. Always we have had temporary tables stored in memory. This is easy on one server, but if we have to scale this will not work as is. In our new approach, we are having a primary server handle long queries and place its results into temporary tables. Secondary servers just utilize these temporary smaller tables. When the primary server is refreshing, I don't want the secondary servers to try to wait or update their local caches. As time is progressing, I am thinking of just using a lock table to represent states of each of these reads/updates, but I am not loving the solution. Having such a method means you have to maintain the locks, which is never a flavor I like. I am all done except for this locking issue. John -- View this message in context: http://www.nabble.com/Locking-entire-table-tp15035646p15114747.html Sent from the Apache DB - ObjectRelationalBridge Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
