When people request information about communications, my first instinct is to jump to respond with a reference to mv.NET. I seriously do refrain from most such ads. Please note however that mv.NET is good for the sort of "Push from MV" request that we see here. It's also good for integration with relational databases, for Web Services, for XML handling, for SOA, for website and thick-client development, and for so many of the other requests we see here. If you have any questions about how to do something, just remember that mv.NET is probably one of many viable solutions. More importantly, rather than using several technologies for a variety of needs, consider the elegance of using one tool for almost all of your needs. This is especially of benefit to VARs, to avoid having to install (and maintain) so many different tools on end-user systems.
mv.NET is a suite of libraries for doing many things. As an affirmation of its value, IBM has recently licensed mv.NET so that they can sell and support it. How much more of a stamp of approval can we get? Why not use UO.NET? It's free and a good connectivity pipe but it's a very simple library which requires the developer to write a lot of code to wrap around it. mv.NET already has three useful code wrapped around the pipe, and in fact, mv.NET uses UO.NET as the pipe into Universe and Unidata. Contact me if you'd like to evaluate mv.NET. Nebula R&D is an authorized international reseller of mv.NET and provides product support, training, and related development services. Our resources include a recognized Microsoft C# MVP and other talented Microsoft-certified developers. BlueFinity International has an mv.NET Conference in May in the Miami area. The conference is $99 and attendees receive a complimentary development license for mv.NET. Contact me for details. Thanks and Regards, Tony Gravagno Nebula Research and Development TG@ please.remove.this.anti.spam.textNebula-RnD.com brian wrote: > Pam > > There is a wealth of options open to you, from web services (BASIC > SOAP API), direct socket connections, BCI (ODBC), message queues or > even flat file. > > The key question will be what the other systems support. > > Web services or XML/HTTP are all the vogue, and can be done > reasonably easily from U2 platforms. > > Brian > > We have a need to push data to another system. Hopefully, out a port > that will acknowledge the receipt of the data. We need to send HL7 records > from a hospital system to a radiology system. Any help would be appreciated. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
