Re: Lightweight RPC over BEEP
Francis Brosnan Blazquez <[email protected]> Fri, 30 Dec 2005 18:58:23 +0100
| Newsgroups | gmane.ietf.beep |
|---|---|
| Organization | Advanced Software Production Line, S.L. |
| Message-ID | <[email protected]> |
El vie, 30-12-2005 a las 09:06 -0500, Peter Hall escribió: > Francis Hi Peter! > > Just a quick thought about your location service. > > I can think of 2 possible ways to do this. > 1) LDAP - http://www.openldap.org/software/ > 2) DNS Service Discovery - http://www.dns-sd.org/ > > I've not implemented a location service but I know both of these > solutions > are capable of doing it. Thanks for your reply, I'll take a look into DNS Service Discovery. I feel both are centralized location service solutions for large networks (and not so large ones ;-) that could allow to find new BEEP servers that are allways located on the same host:port place (maybe changing the port part). However we have already implemented that server location behaviour in the middle-ware we are working on called Af-Arch [1]. But, at the client side, to perform desktop IPC between applications to compose bigger ones running on top of Af-Arch we have realized that, already being attached to a BEEP engine, why don't use that engine to connect to other components thourgh an lightweigh RPC rather than going to use other IPC? In our environment we have several desktop IPC solutions, the one that could fit well is D-BUS [2], but they don't seem to understand that people not only want's to produce KDE and GNOME desktop based applications, because customer are mostly running windows!! (for D-BUS people, windows desktop doesn't exist, and that's ok [3]) If you look inside D-BUS source code, you'll find that they are reimplementing (*again*) many concepts already address by BEEP. So, we could say we are looking for: 1) Reuse the BEEP engine, that our applications is already attached, to implement a portable (starting for GNU/Linux and Windows) IPC mechnism that, if posible, to be one an already defined RFC. At this moment we are mostly sure that XML-RPC (RFC3529) is a good starting point. 2) Find and implement (or just implement) a mechanism to discover inside the same desktop more BEEP peers exporting component interfaces on top of previous defined mechanism. Thanks for your comments Peter, feedback is allways appreciated!! Cheers, [1] http://fact.aspl.es [2] http://www.freedesktop.org/Software/dbus [3] http://dbus.freedesktop.org/doc/dbus-faq.html (item 18) > > Regards > Peter -- Francis Brosnan Blazquez <[email protected]> Advanced Software Production Line, S.L.