I need to do this too.
My idea (I have not done it yet) was to load up a file completely into memory and then use JMS to store and forward the file to another JMS on another server. Thus creating a JMS to JMS-bridge.
I need to queue them in case the JMS at the other end isn't up (so, I can resend later) and also I am not allowed to write the files out anywhere and so I cannot have a virtual reference to them. I have to have them in memory.
Once on the end JMS queue, I then have to use FTP to transfer it (this machine only has an FTP server on it). So, I am going to stream it from memory once it’s moved around.
This is how I was going to do it. But maybe your SAAJ approach is better.
I am still at the thinking stage at the moment.
Regards Rick
bgoetzmann <[EMAIL PROTECTED]>
28/03/2006 14:18 | To: [email protected] cc: Subject: Transfering large files |
Hello,
Using ServiceMix, what is the best strategy to transfer large files (size
greater than 10 Mo or more) between two services connected on the bus. With
what components ? With what limitations ? I think for example to the SAAJ
component (attaching a file to a message).
A good point would be the possibility to monitor by another service, the
progression of the transfer ; in this case, I suppose you must breakup the
file into smaller packets for transmission.
I appreciate any suggestion or experience !
--
View this message in context: http://www.nabble.com/Transfering-large-files-t1355591.html#a3629363
Sent from the ServiceMix - User forum at Nabble.com.
Direct Line Group Limited, registered in England with number 2811437, registered office 3 Edridge Road, Croydon, Surrey CR9 1AG. The following companies are members of the Direct Line Group: Direct Line Insurance plc, Direct Line Life Insurance Company Limited, Direct Line Unit Trusts Limited and Direct Line Financial Services Limited, all of which are authorised and regulated by the Financial Services Authority. All are members of The Royal Bank of Scotland Group. |
This email is intended for the addressee only and may contain confidential, proprietary or legally privileged information. If you are not the intended recipient of this email you should notify us immediately and delete it. You should not copy, print, distribute, disclose or use any part of it. We reserve the right to monitor and record all electronic communications through our networks. We cannot accept any liability for viruses transmitted via this email once it has left our network. |
