I was going to say that the "transactionblocking" config var in T2K was removed from Witango 5. You might also find some references to a parameter used in the dsconfig which would allow you to specific a dbms as single threaded, this too has been removed. There is no longer any mechanism in Witango which can, by itself, support transactional operation or blocking.
Many of these removed options were very confusing, and were added to deal with bad/missing db behavior with older dbs like filemaker and pervasive 7. Witango introduced a complete rethinking of how to deal with databases, which can be summed up as: Witango does everything it can to complete its requests, and leaves the db to fend for itself. Robert -----Original Message----- From: Customer Support [mailto:[EMAIL PROTECTED] Sent: Thursday, June 03, 2004 11:21 PM To: [EMAIL PROTECTED] Subject: Re: Witango-Talk: BeginTransaction - EndTransaction section: does it really work? > transactionBlocking: This configuration variable determines whether > Witango Server blocks other processes during a transaction. Default: > true. > What exactly "block other processes" meant could be debatable due to > lack of better information. To me it meant: one single process gets > access to the DB. � > I have just checked with the engineers. This functionality was a T2K feature only. I have notified the doc writers to remove it from the next release of the documentation. Witango Support ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
