You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Carl Trieloff (JIRA)" <qp...@incubator.apache.org> on 2006/10/12 18:19:36 UTC

[jira] Updated: (QPID-34) Introduce staging for file transfer

     [ http://issues.apache.org/jira/browse/QPID-34?page=all ]

Carl Trieloff updated QPID-34:
------------------------------

    Description: 
The AMQP protocol specification touches on file transfer briefly. However, in order to support file transfer we need to introduce a staging mechanism for managing data transfer, particularly with large files.

There has previously been much debate about the appropriate handling for this requirement, from protocol to broker. This task requires more detail before it can be progressed, but adding as a placeholder.

--->
There have been discussions in the working group to solve this more elegantly. I believe the suggestions will be posted publically soon and it would be good to wait for that and then provide feedback / build based on that.
<--

  was:
The AMQP protocol specification touches on file transfer briefly. However, in order to support file transfer we need to introduce a staging mechanism for managing data transfer, particularly with large files.

There has previously been much debate about the appropriate handling for this requirement, from protocol to broker. This task requires more detail before it can be progressed, but adding as a placeholder.




> Introduce staging for file transfer
> -----------------------------------
>
>                 Key: QPID-34
>                 URL: http://issues.apache.org/jira/browse/QPID-34
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>            Reporter: Marnie McCormack
>
> The AMQP protocol specification touches on file transfer briefly. However, in order to support file transfer we need to introduce a staging mechanism for managing data transfer, particularly with large files.
> There has previously been much debate about the appropriate handling for this requirement, from protocol to broker. This task requires more detail before it can be progressed, but adding as a placeholder.
> --->
> There have been discussions in the working group to solve this more elegantly. I believe the suggestions will be posted publically soon and it would be good to wait for that and then provide feedback / build based on that.
> <--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira