It does not naturally support chunking. On Thu, Jun 30, 2011 at 12:51 PM, Dheerajgoswami <[email protected]>wrote:
> I had an impression that thrift does support chunking mechanism for large > data transfer. Is that not true? > > Thanks > Dheeraj > > > On Jun 30, 2011, at 11:50 AM, Bryan Duxbury <[email protected]> wrote: > > > Thrift is not particularly suited to sending large files. In particular, > > Thrift structures need to be fully in-memory before they can be > serialized > > and sent. You could implement a multi-message transfer mechanism, though. > > > > On Thu, Jun 30, 2011 at 9:29 AM, Yuri Bochkarev <[email protected] > >wrote: > > > >> Hello. > >> > >> > >> Can you tell me please if Thrift is good for sending large files in > >> LAN? If so, can you point me to some examples? > >> > >> I have a server written in Erlang and a client written in Python. > >> Beside of simple communication protocol which Thrift is perfectly good > >> for, server also needs to send large (up to several gigabytes: > >> 50Mb..5Gb) files to the client and to get same large files back. The > >> process must be reliable (we must detect network failures and send > >> file again) and resumable (if network connection drops, it would be > >> nice to continue sending from the point where is was stopped, like > >> FTP). The latter requirement is not that important, actually. > >> > >> The communication is expected to happen in LAN. Will Thrift > >> implementation properly handle such a large binary messages? > >> > >> > >> Thanks in advance, > >> Yuri > >> >
