Currently wRPC framing is optional - that significantly hurts usability and complicates the public APIs.
At the same time, the only "official" wRPC transport not using the default wRPC framing is NATS.io.
The proposal is, therefore, to drop the "custom framing" feature and simply always use wRPC framing.
That should let us drop the Index trait and other obscure abstractions that were built to support this flow.
This does mean that NATS.io transport as it is today would need backwards-incompatible changes and I'm currently thinking that simply removing NATS.io support altogether would be the simplest way forward.
Currently wRPC framing is optional - that significantly hurts usability and complicates the public APIs.
At the same time, the only "official" wRPC transport not using the default wRPC framing is NATS.io.
The proposal is, therefore, to drop the "custom framing" feature and simply always use wRPC framing.
That should let us drop the
Indextrait and other obscure abstractions that were built to support this flow.This does mean that NATS.io transport as it is today would need backwards-incompatible changes and I'm currently thinking that simply removing NATS.io support altogether would be the simplest way forward.