# Missing detailed docs on RPC implementation (integration with other frameworks)

**URL:** https://discourse.nameko.io/t/missing-detailed-docs-on-rpc-implementation-integration-with-other-frameworks/314
**Category:** Github Issues
**Created:** [August 13, 2018, 9:33am UTC](https://discourse.nameko.io/t/missing-detailed-docs-on-rpc-implementation-integration-with-other-frameworks/314 "2018-08-13T09:33:17Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![mattbennett](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.nameko.io/mattbennett/32/13_2.png) [@mattbennett](https://discourse.nameko.io/u/mattbennett)
#### Post date: [August 13, 2018, 9:33am UTC](https://discourse.nameko.io/t/missing-detailed-docs-on-rpc-implementation-integration-with-other-frameworks/314/1 "2018-08-13T09:33:17Z")

</div>

_From @izmailoff on Thu Sep 01 2016 02:57:41 GMT+0000 (UTC)_  
  
Hi, I’m trying to implement support for RPC in my non-nameko service that connects to RabbitMQ (AMQP). I wasn’t able to find any description of how RPC exchange should happen.

I can see that Nameko is serializing RPC call to JSON - this is what I receive on subscriber side: `{"kwargs": {}, "args": ["test string"]}`. I’ve figured that the queue will be named as `'rpc-' + my_service_name`. It seems that there is another exclusive queue created with GUID appended to it’s name, which I suppose is used for the response.

Do you have any docs or quick info on how exactly RPC exchange happens? It would save lots of reverse-engineering effort for anyone trying to integrate with nameko.

Thanks  
  
  
_Copied from original issue: [https://github.com/nameko/nameko/issues/354](https://github.com/nameko/nameko/issues/354)_