Nando,

>A> A third is that the protocol is antiquated and not at all
>A> appropriate for local communication.
>
>It's not appropriate for high-latency networks either. I have read on
>the lists that the protocol would have been revised for FB2 but I
>don't see it happening in FB2 nor in FB3, as there hasn't been any
>concrete proposal with enough agreement AFAICT.

There are a couple ways to introduce a new IPC protocol
in Vulcan.

The way it's been done in InterBase/Firebird is to add the
new protocol to the existing remote provider (aka fbclient)
& server code and allow the two ends to pick their favorite
among the available protocols. That allows - or should allow
- any client however old to talk to any server however new.
In theory, the worst that happens is that a newer server
sometimes sends an error code that the older client can't
translate.

With Vulcan, you could introduce a new 'provider' and a
new server process that communicates with the provider.

Regards,


Ann