# Transfer parameters/variables per TCP/UDP socket

**URL:** <https://www.ruby-forum.com/t/transfer-parameters-variables-per-tcp-udp-socket/241413>\
**Category:** GNU Radio\
**Created:** [April 5, 2015, 7:59pm UTC](https://www.ruby-forum.com/t/transfer-parameters-variables-per-tcp-udp-socket/241413 "2015-04-05T19:59:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [April 5, 2015, 7:59pm UTC](https://www.ruby-forum.com/t/transfer-parameters-variables-per-tcp-udp-socket/241413/1 "2015-04-05T19:59:16Z")

</div>

Hi,

i have two grc applications. One TCP server application and one TCP  
client application. I want to change a parameter with a WX GUI slider on  
the client side and transport it to the server side. My first idea was  
to connect a variable / parameter block with a TCP/UDP block and set a  
specific port. The problem is that i cant connect parameter / variable  
blocks.

Is there any workaround ?

cheers,  
Andy

---

<div class="post-metadata">

**Author:** ![andreas\_l](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/7bcc69/32.png) [@andreas\_l](https://www.ruby-forum.com/u/andreas_l)\
**Post date:** [April 5, 2015, 8:46pm UTC](https://www.ruby-forum.com/t/transfer-parameters-variables-per-tcp-udp-socket/241413/2 "2015-04-05T20:46:21Z")

</div>

i want to correct myself. I dont want to transfer the parameter/variable  
itself. I want to transfer the content of it.

Am 05.04.2015 um 19:57 schrieb Andreas L.:

---

<div class="post-metadata">

**Author:** ![andreas\_l](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/7bcc69/32.png) [@andreas\_l](https://www.ruby-forum.com/u/andreas_l)\
**Post date:** [April 7, 2015, 4:40am UTC](https://www.ruby-forum.com/t/transfer-parameters-variables-per-tcp-udp-socket/241413/3 "2015-04-07T04:40:54Z")

</div>

If you don’t mind a write-only interface, you can use xmlrpc

> **[gnuradio-examples/xmlrpc\_control at master · ckuethe/gnuradio-examples](https://github.com/ckuethe/gnuradio-examples/tree/master/xmlrpc_control)**
>
> master/xmlrpc\_control

On Sun, Apr 5, 2015 at 11:44 AM, Andreas L.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> > side and transport it to the server side. My first idea was to connect a
> > 
> > * * *
> > 
> > Discuss-gnuradio mailing list  
> > [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> > [Discuss-gnuradio Info Page](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio)
> 
> * * *
> 
> Discuss-gnuradio mailing list  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [Discuss-gnuradio Info Page](https://lists.gnu.org/mailman/listinfo/discuss-gnuradio)

–  
GDB has a ‘break’ feature; why doesn’t it have ‘fix’ too?