On Thu, 2009-06-18 at 19:55 +0100, Bruce Simpson wrote: > Hi Ben, > > Ben Greear wrote: > > Please don't add something that is even more bloated and cumbersome > > than XRL! It's easy to wrap c code in c++, and that > > seems to be enough code language support to me (I like Java, but no > > reason to write router code in java > > when the project already supports C++). > > This is why Thrift+AMQP is going to get a lot of sweet personal > attention from me. > I'm not so sure CORBA is the right way to go, but it has its appeal for > some. > > I think improvements in the componentry are needed. XRL has known > limitations. Wielding C++ *is* a professional speciality -- and it's > unreasonable to expect everyone to do it, when protocols can be realized > in languages which are easier to pick up and use. > > Using Java is not my intention, but if someone else wants to, why not? > There are some very low footprint Java VMs out there. >
I'm probably showing some naivety here as I don't know what Thrift+AMQP are other than what a 10 second google search revealed. Being able to use a named pipe to send pre-defined commands and get responses would allow a great many languages to interact with your project. I'm still getting a feel for your architecture and reading the docs so it may not fit in real well at this time. I could connect to the named pipe and send a "REGISTER" command which would allow me to announce my applications presence. I could then send a "CONFIG" command which would include all of the commands that I have available to be called and what events should be sent to me when those commands are entered. My application could then sit and wait for events to be sent and process them appropriately. There could be some standard events which would cause an application to dump properly formatted status data. In a VOIP context I might be returning the list of available call routes for the LCR module in Kamailio. Just some thoughts, it may be outside the scope of your project and too much of a detour from network routing but call routing can be dealt with quite similarly. -Jonathan _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
