I took a look at the Pipes. It looks like a great idea. Does it work only in C++? Would it work in a JVM environment?
On Mon, Oct 15, 2012 at 2:18 PM, Juan Moreno <[email protected]>wrote: > Hey Jens & Peace, > > Thanks for your answer. I was not talking about any language in > particular. > In the model I have in mind, a Java Client would launch several services > in separate processes and make service calls to them. > This would allow calling methods on a variety of languages. > > In other words, for a given service launch a sub-process and call it over > STD IN. I am going to look into the pipe transports. > > Gratefully, > Juan > > > On Fri, Oct 12, 2012 at 1:24 PM, Jens Geyer <[email protected]> wrote: > >> Hi Juan, >> >> >> I think it may very well be possible to have a TTransport and >>> TServerTransport done over Standard In/Out. >>> >> >> What particular language are you talking about? There's existing support >> for anonymous pipes as well as an TFDTransport for a few languages. >> >> >> This would be used when creating child processes. >>> >> >> The pipe samples do exactly that. The server starts a client process and >> they communicate via anon pipes. Since the creating process controls the >> std-Handles of the created process (at least with Windows), this should be >> possible. >> >> >> The implementations would need to be created in all the various >>> languages. >>> >> >> You are welcome to use the existing code, learn, ask and contribute an >> implementation in your favourite language. :-) >> >> http://thrift.apache.org/docs/**HowToContribute<http://thrift.apache.org/docs/HowToContribute> >> >> HTH, >> JensG >> >> >> -----Ursprüngliche Nachricht----- From: Juan Moreno >> Sent: Friday, October 12, 2012 6:15 PM >> To: [email protected] >> Subject: Standard In/Out >> >> >> Hey All, >> >> Since Thrift chose not to assume you would be using TCP/IP for transport >> all the time, they abstracted it like they did the Protocol. >> I think it may very well be possible to have a TTransport and >> TServerTransport done over Standard In/Out. >> This would be used when creating child processes. The implementations >> would >> need to be created in all the various languages. >> >> Is this something that anyone is interested in? >> It's just another option for Inter-Process communication besides Sockets. >> > >
