# TCP Output Node: Needed Clarification; Please Help

**URL:** <https://discourse.nodered.org/t/tcp-output-node-needed-clarification-please-help/2846>\
**Category:** General\
**Created:** [4 September 2018 18:43 UTC](https://discourse.nodered.org/t/tcp-output-node-needed-clarification-please-help/2846 "2018-09-04T18:43:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [5 September 2018 13:38 UTC](https://discourse.nodered.org/t/tcp-output-node-needed-clarification-please-help/2846/9 "2018-09-05T13:38:45Z")

</div>

Over on [this discussion thread](https://discourse.nodered.org/t/function-buffer-to-outputs/2874/2), I was just lamenting that fact that I couldn't find a way to convert an incoming buffer (containing a json string) to an actual javascript string -- short of using a `function` node to invoke the toString() method...

> [@dceejay](#):
>
> Or indeed maybe a string to buffer parser node that does handle \r\n and/or STX/ETX type syntax and vice-versa

+1 Sounds like that would be useful for me as well.

---

_[View the full topic](https://discourse.nodered.org/t/tcp-output-node-needed-clarification-please-help/2846)._