Postgres's latest drivers seem to support streaming. They do so in 4k blocks, but thats pretty okay.
There is another reason to use the store :-). JBossMQ...it...well makes multiple copies of the body. Ultimately we will need BOTH behaviors (Store and No Store). For this release Store-only is fine. This is a bit of a feature regression in that there are going to be people who might send the messages over JMS to other servers with other DBs. However, I can live with that for now because those people....well....they are a little cracked (that *won't* perform well). For the present you'll be limited to one DB on the same server as JBossMQ. Eventually there should be: 1. Always use store 2. Never use store 3. Use store when the message is > N kb So while I'm only asking for #1 for M3, don't code yourself into a corner with #2, #3 for M4 :-) i also think this is a great! Glad you guys are talking! This all looks like great work! -Andy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869707#3869707 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869707 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
