recently I have been doing, well, pretty much nothing wrt cad. recently has been obsessing on network protocols (xmpp and xml-rpc in particular...). then in my bit of fantasizing, I am imagining apps using im and rpc for integrating with each other, sharing data, ... this could possibly have interesting uses wrt cad, but, one can probably guess how strong my ties are to any particular point of obsession for any length of time. if anything, I was considering the idea that the front-ends (moddelers, renderers, ...) would be seperated from the back end (a kind of geometric db or such), eg, by a layer of network protocol or rpc... it may be a while before I do much of any real work on my cad again though... anyways, recent work has largely been focused on the network front (and building the framework required for some of my more recent extensions). here are some specs related to the protocols of interest (for which I have flogged endlessly recently): http://www.xmlrpc.com/spec http://www.jabber.org/jeps/jep-0009.html http://www.jabber.org/ietf/draft-ietf-xmpp-core-22.html http://www.jabber.org/jeps/jep-0078.html (all these I have had implemented for quite a while...). and here is a spec for an extension mechanism: http://bgb-sys.sourceforge.net/2004-01-18_XMLNS_EXT_XMLRPC.html an annoyance is building the infrastructure required by my extension mechanism (to actually be useful) has required fairly signifigant alterations to my xml-rpc related code... it requires a bit more work than it would first seem (eg: to make it so that on the api level the protocol gains the ability to be more readily extensible, maintaining info about peers, ...). lots of work is generally needed throughout my network code if I have any real hope of trying to once again persue the idea of the "application mesh"... I am unsure if any here would have any real interest in this kind of thing... -- cr88192 at hotmail dot com http://sourceforge.net/projects/bgb-sys/ http://bgb-sys.sourceforge.net/