DisplayToLogical converts external input to internal format.
if you have an object everything is internal already.
what would you expect to convert?

DisplayToLogical is just not involved in that process.
You may eventually look for LogicalToStorage  -  [a rare case]

I'm full with you.
And if you aren't under time pressure you get a close look at things that have become obsolete over time but never were removed.

That's good news! and a real surprise! 
I appreciate it highly

 

I'm not sure what the first 2 bytes are but $ZCVT(anystring,"O","UTF8") should do the conversion
and this works for strings up to ~3,6 MB with Long-String enabled in your installation

for $ZCVT: https://docs.intersystems.com/iris20201/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_fzconvert

in OEX there is a series of various  Websocket Clients I produced:
The internal is just available in IRIS.
Half Externals (eg. CSP based, using JavaScript )  might fit also for Caché 2015 as for IRIS
check WebSocketClient CSP based

 

You mention: web application configuration information, task plans, sql gateway, etc
Namespace %SYS was always excluded from MIRROR  since most of the information is
either static (SYSLIB)  or server-specific (eg. journal)
 

@Alexey Maslov
I had a similar experience with "InPlace".
This may work if your applications are as simple as in SAMPLES:
[ "nome est omen" SAMPLES => Simple]
Just a few $ZU() or other %z* stuff may break you, or file references containing *CACHE*.
Or some $ZF() functions with c-binding, ....
Therefore I designed my "2 worlds" approach using ECP as a data bridge: 
Using ECP across IRIS and Caché

Ah much better! 

confirmed! same result with me

Definitions might be wrapped into some $$$macro that calls the .INT directly.
Similar to some compiled class . Deployed classes provide more comfort.

hi @Сергей Марушко

it is done.  Using ECP across IRIS and Caché

if the deployment is sensitive distribution happens a pure  *.OBJ

Stay tuned! 
I'm almost done (most likely before Monday) with a demo of how you can make a soft transition. 

@11:

1:1 could be a degraded 1:N relationship or
by inheriting  from a base class as mentioned earlier: "Employee Extends Person"

many-to-many can be covered as M:N relationship as I described in my article 3 years ago.

@9.9.  storage is generated once if not existing yet.
you may change it manually (typically data location global) as long as there is nothing stored yet
otherwise you lose the existing content. Or you copy it to the new location.
My article The adopted Bitmap shows such an example [actually also in contest}

6 & 7 are side effects of object inheritance.
Think of a class Person.
But Employee Extends Person
Similar Students Extends Person too
So you have 3 tables but all are Persons  Some with extension some not.  

@6: Table Employee corresponds to class Person and to class Employee

@7: So class person corresponds to Table PERSON, EMPLOYEE , STUDENT

#20. Is slightly exaggerated
official docs present it differently.
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=ITECHREF_json 
https://docs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?LIBRARY=%25SYS&CLASSNAME=%25Library.DynamicArray