<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Ben,<br>
<br>
We have to send file not stream them, because we will transfer
documents no video.<br>
So I am not interested in the Stream class.<br>
<br>
Regarding using SSL -I looked atthe SSL guide
<a class="moz-txt-link-freetext" href="http://www.rabbitmq.com/api-guide.html#ssl">http://www.rabbitmq.com/api-guide.html#ssl</a> but since we'll encrypt I'd
prefer to encrypt the document.<br>
<br>
<br>
<blockquote type="cite">
<pre wrap="">If the issue causes the underlying connection to close, you may want
to want to use the ShutdownListener interface to perform some kind of
recovery, but one what you actually do may depend on how your
application handles resends. Have you implemented any chunking,
streaming or partial acknowledgments? Is this transactional at all?
</pre>
</blockquote>
Yes, we will implement chunking but there will be no transactions. The
use case is as such : <br>
1)The Producer sends a file to The Server.<br>
2) The server stores the file somewhere...<br>
3) The Consumer checks if there any new files for him and if there are
gets it.<br>
<br>
So I need a way to :<br>
1) restart both the sending and the receiving<br>
2) store the files somewhere on the server.<br>
<br>
Reading the 0.8 spec it seems to me that RabbitMQ must provide both. <br>
<br>
Am I wrong?<br>
<br>
<br>
Thanks,<br>
Dimitar<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html; ">
<br>
</div>
<br>
Ben Hood wrote:
<blockquote
cite="mid:269388e30808190121g106c8c0dw1192beef2ff083a3@mail.gmail.com"
type="cite">
<pre wrap="">Dimitar,
On Tue, Aug 19, 2008 at 8:57 AM, Dimitar Bakardzhiev
<a class="moz-txt-link-rfc2396E" href="mailto:dimitar.bakardzhiev@rexintegra.com"><dimitar.bakardzhiev@rexintegra.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Our use case is to provide secure file transfer.
Reading AMQP 0.8 spec it is stated that the protocol itself is secure,
but since there is no encryption mention in the spec we will encrypt the
files we are sending to RabbitMQ.
</pre>
</blockquote>
<pre wrap=""><!---->
Please be aware that the file streaming class specified in 0-8 is not
implemented and probably will be removed from a revised version of the
specification.
</pre>
<blockquote type="cite">
<pre wrap="">So I have two questions:
1) is our approach of encrypting the files correct to the spirit of
RabbitMQ or there is some security built in?
</pre>
</blockquote>
<pre wrap=""><!---->
Have you looked at the SSL guide <a class="moz-txt-link-freetext" href="http://www.rabbitmq.com/api-guide.html#ssl">http://www.rabbitmq.com/api-guide.html#ssl</a> ?
</pre>
<blockquote type="cite">
<pre wrap="">2) how we have to use Java client in order to restart sending of a file
if some transient network issue occurs?
</pre>
</blockquote>
<pre wrap=""><!---->
If the issue causes the underlying connection to close, you may want
to want to use the ShutdownListener interface to perform some kind of
recovery, but one what you actually do may depend on how your
application handles resends. Have you implemented any chunking,
streaming or partial acknowledgments? Is this transactional at all?
Ben
</pre>
</blockquote>
</body>
</html>