On Wed, 2003-06-11 at 16:51, Travis Whitton wrote: > > Concurrency issues can be difficult without a full context. But I think > > this will be a problem. > > Sorry for not providing enough information. Here are the relevant > excerpts from my code:
Sorry, I wasn't actually looking for more context ;) It takes some deep thought, and you have to think about where you want to deal with concurrency, what concurrency you expect, and what your requirements are. If you want to use database-level transactions over several requests, you're probably going to want to keep the connection (with its associated transaction) in the session or something. Then you are going to have to pass that connection in to your objects when setting values, *or* you'll specify that connection when you create your objects, and the object will carry around that connection (and be specific to that user/transaction). It's a long topic, I'm afraid, so this only gives a hint as to how you might go about this. Ian ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
