JMS vs .... ?

Hi,

I've picked up some crufty code to investigate at work, and part of solving the problem is getting data (a pdf) from one machine to another reliably (and then sending a fax). Currently, the code does this via a wonky email routing scheme that depends very heavily on the machine in question being configured 'just so'. Not good...

I was looking at JMS as a potential alternative, but some of the guys in the local JUG didn't seem very enthusiastic about it as a solution, suggesting it might be better to just 'roll my own' - a row in the database that gets updated to say "I've been read" when the file has been fetched via http. Admittedly, that's an improvement over the current system, and seems simpler than fiddling with JMS...

Thoughts?

Thankyou,
--
David N. Welton
- http://www.dedasys.com/davidw/

Linux, Open Source Consulting
- http://www.dedasys.com/
.