I think, the way the abstractions are chosen in this patch, it is still very much tied to how the libpq protocol works. For example, there is a cancel key and a ready-for-query message. Some of the details of the simple and the extended query are exposed. So you could create a protocol that has a different way of encoding the payloads, as your telnet example does, but I don't believe that you could implement a competitor's protocol through this. Unless you have that done and want to show it?
- Re: Extensibility of the PostgreS... Álvaro Hernández
- Re: Extensibility of the PostgreS... Dave Cramer
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreS... David Fetter
- Re: Extensibility of the PostgreS... Álvaro Hernández
- Re: Extensibility of the PostgreSQL wi... Dave Cramer
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreS... Kuntal Ghosh
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreS... Peter Eisentraut
- Re: Extensibility of the PostgreS... Hannu Krosing
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreS... Hannu Krosing
- Re: Extensibility of the PostgreS... Jan Wieck
- Re: Extensibility of the PostgreSQL wire p... Joshua Drake
- Re: Extensibility of the PostgreSQL wire protocol Jan Wieck
- Re: Extensibility of the PostgreSQL wire proto... Tom Lane
- Re: Extensibility of the PostgreSQL wire p... Jonah H. Harris
- Re: Extensibility of the PostgreSQL wire p... Jan Wieck
- Re: Extensibility of the PostgreSQL wire protocol Jan Wieck