Hi, there are two basic use cases from my understanding. First, the optimization of the memory block allocated with one call. Next, the effect of protecting the Server against malformed or garbage binary packets, at least to some extent.
----- Ursprüngliche Nachricht ----- Von: John R. Frank Gesendet: 12.05.2013 13:40 An: [email protected] Betreff: does TFramedTransport assemble multiple frames? Thrift users, The Java implementation of TFramedTransport enforces a maxLength on frames, however when a client respects this maxLength by breaking a message into multiple chunks, it looks like the call to TMemoryInputTransport.java via: readBuffer_.reset(buff); in readFrame just *replaces* the previous frame. Am I reading that correctly? Shouldn't it gather all the frames until the end of the message? Maybe I am misunderstanding the purpose of framed transport? Or maybe there is currently no way to indicate the end of the message, so this just has not yet been implemented and all messages must be less than maxLength if they want to use FramedTransport? If that's the case, then why use FramedTransport? John
