We pushed federation caches over the signalling channel of ISDN2 as late as 2007. ISDN is the most commonly misunderstood and under appreciated communications standard. During the early nineties ISSN acquired a horrible reputation for incompatibility, but the very nature and value proposition of ISDN remains the most adaptable and capable L0/1/2 communications standard that was intentionally designed to adapt to and enable legacy protocols and future transition requirements. This is why the D channel is capable of transfer of user defined packet payloads up to 16kbps. Commonly dismissed as the signalling channel, why was it designated as "D channel " and the commonly presumed data channels, "B channels"?

The myriad problems and factors that assailed practical IDDN adoption in the early days when a working ISDN interface was a genuine wonder not of miracles in configuration but the capability delivered (we ran applications in advertising that had financial trading style requirements for transactions and the fact that advertising copy was delivered via ISDN was the kind of integration that was envisioned originally)

Everyone is confusing me with their apparent over reaction to the connection of cloud to remote sites. This was what CICS was written for fifty years ago. I feel like I'm discussing state secrets every time I mention CICS. Can anyone recall the killer feature of NT3.1? MTS, if you must have it. MTS is why SQLserver was so easily portable to Linux. I suspect about everyone who reads HN might have a ball with some of the desperately not trendy things we are involved in. Like my uncle dusting his suit vests, smiling he only had to wait thirty years for them to return to fashion. This is a universal interval someone who can explain it will deserve a Nobel I'm sure...