On Fri, Apr 13, 2012 at 3:44 PM, Henri Gourvest <hgourv...@gmail.com> wrote: > Le 12/04/2012 13:43, Alex Peshkoff a écrit : >> This will require serious redesign of network protocol. Certainly >> doable. Will require symmetric changes not only in client library, but >> in network server too. Must say that starting with 2.5 posix >> superclassic server and all arcs in 3.0 firebird architecture is very >> well adapted for such change - network server behaves like any other >> firebird client, calling same API as client tasks do. I.e. you can >> easily replace that part of SQL server even not recompiling the rest of >> DB engine. > > Thank you very much for this information, I hope it will be available in > future versions of firebird.
In Firebird 3.x you can write your own protocol , this is what i understand from the pluggable architecture http://www.slideshare.net/mindthebird/firebird-3-providerbased-architecture-plugins-and-oo-approach-to-api I'm thinking that you can write some kind of bson protocol http://www.mongodb.org/pages/viewpage.action?pageId=16646453 to your own plugin Client->bson/json/redis protocol-> your own v8 node js plugin -> firebird 3.x engine https://github.com/xdenser/node-firebird-libfbclient ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
