2008/5/28 TLFox <[EMAIL PROTECTED]>: > What I would suggest is to add a flag so users can choose whether persistent > messages are sent sync or async. That can default to async so you get better > performance, but you need some way of letting users get normal JMS > behaviour. Otherwise you risk losing customer data, since believe me, JMS > users will assume persistent messages are sent sync (every other system I > know does it this way).
In a similar style, Tibco EMS does not by default do an fsync on publish (i.e. you cannot be sure it has reached storage). That presumably makes them look better in benchmarks where people don't read the docs. (There is a flag to make it fsync). I would support the addition of a flag to make non-txnal sends synchronous but we have not had any user demand for this yet - many people have asked about this but have been happy to use txns. RG
