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.

It's the task of the application that uses ^CacheTempUser.*  to take care of the housekeeping.
I found no traces that it belongs to Caché System Management and Operation.

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 !

Hi Evgeny,

IF you can afford a short OFFLINE state:

#5)  dismount DB / copy of cache.dat to a fast local device / remount it
      move the copy in a secure place: #2, #1

ELSE IF you have to remain online all the time:
#3)  on fast local device + move backup in secure place by #2,#1
 

NEVER #4) a fair chance for massive inconsitency

Robert
[semper fidelis]

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

I'd suggest in this case to take the original JSON String from Request.HttpResponse.Data
and split it by "LineNumber":

eg:

and you get 

line=3
line(2)=0
line(3)=1

I admit it's not very object-ish but efficient

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.