|
Perhaps I'm still thinking too data-centrically rather than middleware-centrically.
I plan to have a database that stores Commands. There will be many net-facing servers that need to write Commands to the database. Originally this would have been done by performing an INSERT SQL statement from each of the hosts. The database's concurrency mechanisms keep things straight.
With Ice, I would instead define an insertCommand() interface in slice, implement the servant and run it on the database server. I would alsocreate a FreezeMap for the Commands that insertCommand() would use to insert into. The net-facing servers then simply call insertCommand().
From what you've described, I get the impression that as long as I only have one FreezeMap instantiated at any given time (i.e., no possibility of concurrent write access), then things will be fine, which is what I would expect.
Just in case I need it (maybe I don't), if I create one FreezeMap within a read-only transaction and another within an update transaction, then there shouldn't be a problem, right? As long as I don't try to update the database.
Thanks,
Ken Carpenter
|