for this cases a possible solution could be 

%Stream.Global has a FindAt method that could give you a position of  "\u00"

[Find the first occurrence of target in the stream starting the search at position. ]

http://docs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?…

But: if you are on the decoded stream all non printables are just single characters. No issue to cut it in pieces

• read your source stream in reasonable sized junks
• clean out what ever you need
• append it to a temporary stream
• loop on source until you hit AtEnd condition
• finally replace your source either by "copyFromSteam" method [temp -> source]
  or replace source stream reference by temp stream reference

I guess the whole code is shorter than this description.

I'd suggest not to touch the global under the source steam.

of course it makes sense!

but then you know which application is using it and can use the application's cleaning method / routine that takes care of all kind of dependencies:
I remember well times when routines used to start with  KILL ^CacheTemp*($JOB)
I expected over time most applications are using PPG  (^||myGlobal...) to avoid this. Or have a Clean-Up.

So for a first check if this  is the only issue just throw the full string into a $TRANSLATE
$tr(jsonstring,$c(26)) and whipe it out.

e.g.
ZNAMESPACE "%SYS" 
be careful !

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

there isn't much doc around.

it's also used for "Find in files"

a little bit in debugging

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY…

You are right, the A -B -C case isn't covered by me:
not a goal but an assist (half points )

your private google search service delivered some material.
[this is not a standard service]

Athanassios,

I googled some time around Python console:
It  is single threaded.  
But your expectations seem to be that the behavour is like a terminal.

To achieve this your have to run 2 Phyton consoles / shells as you required 2 Terminals.
a) 1 passive to receive messages from WRITE  see attaches example starting before b)
b) 1 active to trigger action in Caché

Your initial code from your questions using the Caché Phyton binding covers b) OK!

for a) you may use a listener similar to this Phyton example with the correct port, buffer,...  ToDo

   1 #!/usr/bin/env python
   2 
   3 import socket
   4 
   5 
   6 TCP_IP = '127.0.0.1'
   7 TCP_PORT = 5005
   8 BUFFER_SIZE = 20  # Normally 1024, but we want fast response
   9 
  10 s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
  11 s.bind((TCP_IP, TCP_PORT))
  12 s.listen(1)
  13 
  14 conn, addr = s.accept()
  15 print 'Connection address:', addr
  16 while 1:
  17     data = conn.recv(BUFFER_SIZE)
  18     if not data: break
  19     print "received data:", data
  20     conn.send(data)  # echo
  21 conn.close()

Hi  Athanassios,

you can not run the sender code in the same terminal as the receiver code
you have to use 2 terminals:

Terminal #1) start receiver. This simulates your Phyton Console

now you wait for something to be sent:

#Terminal #2): run sender

for this test it's essential that the sender finds a receiver waiting for input. Probably the same issue with PhytonConsole?

It's like real life: If nobody listens, your words are lost.   And it has to happen at the same time.

The ouput goes to port 4200. That works with Caché.  (see test code)

Attention:  The ! at the end of the WRITE is important as it triggers the send.
in SAMPLES it is at the beginning:  So you just get an empty line. and rest remains in buffer.
You may also add  WRITE !! before the CLOSE to flush the buffer and send an empty line for termination .
I have no knowledge on Python or PythonConsole but from your code I see no indication
where it starts listening at port 4200. pls. check.

Test code from Caché Terminal:

[ <READ>  is the reaction to the connection CLOSE of the sender as I don't check termination ]

Sorry, I saw just that one Print method fromSAMPLES.
The redirect is especially required to convert a Write Command to a Write() Method and vice versa.
For "classic" devices as files , TCP, UDP, all kind of pipes ,SPOOL,Console, Teerminal,...all you find in Caché I/O Device Guide I just see no added value  except fiddling around $P which I never had the need to do over 40yrs

you insert the object to itself ????

do context.MainObj.IssuesList.Insert(context.MainObj)

really ? does this make sense ??

I woldd expected something like:

do context.MainObj.IssuesList.Insert( tmpObj )

or

do context.MainObj.IssuesList.Insert(context.tempZenObj )

COS shorthand is hard to read in browser;
I personally prefer full size COS + Courier as font.

you missed the $TRANSLATE(.....," ",0) around
pls. set the hook to your preferred solution