Hi Jelle,
I lied. I use the TStreamTransport. See examples below.
archivedTicketHeader is a thrift object generated from the thrift IDL
compiler. I'm using C#.
SERIALIZING
using (var ms = new MemoryStream(header))
{
using (var transport = new TStreamTransport(null, ms))
{
var protocol = new TCompactProtocol(transport);
archivedTicketHeader.Write(protocol);
return header;
}
}
DESERIALIZING
using (var ms = new MemoryStream(header))
{
using (var transport = new TStreamTransport(ms, null))
{
var protocol = new TCompactProtocol(transport);
var archivedTicketHeader = new ArchivedTicketHeader();
archivedTicketHeader.Read(protocol);
return archivedTicketHeader;
}
}
On Fri, Aug 2, 2013 at 9:22 AM, George Chung <[email protected]> wrote:
> I just use the serialization mechanism without any of the transport
> plumbing.
>
>
> On Fri, Aug 2, 2013 at 3:06 AM, Duives, J. (Jelle) <[email protected]>wrote:
>
>> Dear thrift mailing list,
>>
>> We're using thrift for a project having multiple modules on a single
>> system. These modules communicate over thrift and therefore we would like
>> to send the information over the system memory. Is that possible, and if
>> yes, do you maybe have a simple example for me?
>>
>> Another questions is about a single-server, multiple-client connection.
>> Right now we are using the TSocket and TServerSocket as connection.
>> However, on a single system we have one server that should be reachable by
>> two clients. Is that possible without having to recreate the socket every
>> time the client calls the server?
>>
>> Kind regards,
>>
>> Jelle Duives
>>
>> This e-mail and its contents are subject to the DISCLAIMER at
>> http://www.tno.nl/emaildisclaimer
>>
>
>
