[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[xmlblaster-devel] Re: [xmlblaster] Bugging me.
> Ahh, it would be great if you could add your Windows C++ compiler settings
> to our build.xml file
No problem, a week or so, it is turning into a very busy work week for me.
> Possibly it would be nice to allow using our C++ code to use
> lowlevel the SOCKET C-lib one day in future - this way
> C++ clients would use xerces and STL and www.boost.org Threadlib
> and other nice C++ libs but can choose lowlevel between CORBA or
I can see the point in an embedded situation, I not even sure that that the
full socket api is available on those types of platforms (select, ioctl etc)
so dont limit yourself to a common denominator.
I think it would be good/wise to keep the underlying transport mechanism as
pluggable as possible. I think xmlBlaster is 'great' but the strongest
reason I considered xmlblaster is on the client side I already had an
established application and it is all on the strength of CORBA idl that I am
able to work with xmlBlaster seamlessly without adding additional untrusted
comms code. I think the same may stand for a socket based apps, what do you
Have you heard of ACE http://www.cs.wustl.edu/~schmidt/ACE.html