I've never tried to use it for inter-thread/process communication, but I assume it would work. I just don't know why kind of overhead it would be in comparison with using ZeroMQ for the same solution. ZeroMQ seems a bit lighter-weight but I guess it depends on exactly what you are doing.
I've been using it in situations where our application server is written in Java, and we need python, C++, and jquery clients to access it. It makes it really nice to have a consistent API between any of the languages that is auto-generated for you. Thrift takes care of type checking, serializing/deserialzing, sending/receiving. On Tue, Mar 18, 2014 at 10:08 AM, Marcus Ottosson <[email protected]>wrote: > Ah, interesting. I've only looked briefly at Thrift. > > Would you recommend Thrift for inter-thread/process communication, as well > as for communicating across languages? What other languages do you find it > useful to bridge with RPC at the moment, and for what? > > > On 17 March 2014 19:33, Justin Israel <[email protected]> wrote: > >> I'm not sure what inspired me specifically to do that. It just seemed >> appropriate to make it easy to export functions as services and then make >> them discoverable when queried. I figured it was useful to be able to have >> first class registration of what is available remotely. I've actually never >> used RPyc yet. >> >> Currently for my RPC solutions I am working with Apache Thrift. It allows >> you to generate bindings for all the modern languages so you can have a >> server in one Lang and 5 clients each in different langs. It handled all of >> the network aspects and wire formats. >> On Mar 18, 2014 8:11 AM, "Marcus Ottosson" <[email protected]> >> wrote: >> >>> That pretty much sums up my impression of 0mq as well (having used it >>> for about a week). >>> >>> About pyRpc, what inspired the use of publishing methods towards a >>> server? Seems a common pattern in RPC implementations, perhaps that's what >>> RPC is all about? RPyC (my only other experience) uses the same concept, >>> except it publishes them to a separate class (a "Service") that gets passed >>> into the server upon instantiation. What are you using for RPC currently? >>> >>> >>> On 17 March 2014 18:33, Justin Israel <[email protected]> wrote: >>> >>>> I threw that code together when I was first learning ZeroMQ and wanted >>>> to play with the idea of making it a simple RPC mechanism. Turned out some >>>> guys at RedHat were using it and asked for some more thing, so I expanded >>>> it a bit more. >>>> >>>> I really like ZeroMQ. Its a lot of lower level elements that allow you >>>> to put together the patterns you need. While I didn't use pyRpc very much, >>>> I did use ZeroMQ for other things like pubsub. I think its really strong >>>> for a number of use cases, with RPC just being one of them. Its good for >>>> when you want to seamlessly scale work from interthread to interprocess to >>>> local network to even remote network situations, since all that changes is >>>> the socket types and devices you use to connect them. >>>> >>>> Its just a really flexible library for communication, messaging, and >>>> concurrent processing. >>>> On Mar 18, 2014 5:13 AM, "Marcus Ottosson" <[email protected]> >>>> wrote: >>>> >>>>> This is especially targeted towards you, Justin, as I just found this.. >>>>> https://github.com/justinfx/pyRpc >>>>> >>>>> ..as I was looking around for inspiration on how to implement the very >>>>> same thing! >>>>> >>>>> How was your experience with 0mq for RPC? Are you still using this >>>>> implementation or any like it? Are you still using 0mq? If so, what for? >>>>> >>>>> For everyone else, are you using 0mq? What for, and what have your >>>>> experiences been with it so far? >>>>> >>>>> Best, >>>>> Marcus >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Python Programming for Autodesk Maya" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/python_inside_maya/61159046-f043-4a56-b2a5-a67ef77fc178%40googlegroups.com<https://groups.google.com/d/msgid/python_inside_maya/61159046-f043-4a56-b2a5-a67ef77fc178%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Python Programming for Autodesk Maya" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0Q3jCB6Btv45AM90BKGeMszKfzTMwyftTPRFhfPxF5Lg%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0Q3jCB6Btv45AM90BKGeMszKfzTMwyftTPRFhfPxF5Lg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> >>> -- >>> *Marcus Ottosson* >>> [email protected] >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Python Programming for Autodesk Maya" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAxswLjnC%2BebKkx_F%2BNe4G-D6iZxdqE3E6Xb5YDkH-M6Q%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAxswLjnC%2BebKkx_F%2BNe4G-D6iZxdqE3E6Xb5YDkH-M6Q%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Python Programming for Autodesk Maya" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA3jevShCpFOd740q0KXvAOY50x3H3cq60uYS6-94fppPw%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA3jevShCpFOd740q0KXvAOY50x3H3cq60uYS6-94fppPw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > *Marcus Ottosson* > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAfynu1PYkpkoecBGcOSJSNkWGFH9tdeNjqkcakHGj_mQ%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOAfynu1PYkpkoecBGcOSJSNkWGFH9tdeNjqkcakHGj_mQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA1JhAE6Kxt6LG-SvqpMCXr9ETtz%2BetaF2N2NsJ_iHzAsg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
