performing one command (like xquery, add, delete etc.) This would be the best
Thats the way it is. Note that all commands are atomic transactions, like a alter database -> closes the database, renames it and reopens it...but you havent care about that.
Kind regards and happy new year (with BaseX), Andreas
Am 31.12.10 11:06, schrieb Jan Vlčinský (CAD):
Hi Andreas It seems, like I was too smart (and learned a lot about concurrency in AMQP this very long night) :-)
What are starting/ending points of one transaction
- creating connection - closing it. probably not
- open database - close ??
- performing one command (like xquery, add, delete etc.) This would be the best
Jan
2010/12/31 Andreas Weiler <andreas.weiler@uni-konstanz.de mailto:andreas.weiler@uni-konstanz.de>
Hi Jan, if a writing or reading transaction is active, all new incoming transactions are stored in a waiting queue. So all writing transactions will be processed in first come - first server order. Reading transactions are processed concurrently. Transactions will no be rejected at any time. Kind regards, Andreas Am 31.12.10 10:40, schrieb Jan Vlčinský (CAD): one collection can be written/modified only by one process at given moment, other attempts to write are rejected and these attempts will fail. In other words - one collection can be opened only by one process (or are multiple opening clients allowed as long as the do not modify database concurrently?)-- *Ing. Jan Vlčinský* CAD programy Slunečnicová 338/3, 734 01 Karviná Ráj, Czech Republic tel: +420-597 602 024; mob: +420-608 979 040 skype: janvlcinsky; GoogleTalk: jan.vlcinsky@gmail.com mailto:jan.vlcinsky@gmail.com http://cz.linkedin.com/in/vlcinsky