Just to clarify - mv.NET can use standard UO but has also been enabled to use UO.NET for a long time now, and standard UO might not even be supported in a near-future release. It's preferable to use managed components all the way through, so UO.NET is the preferred pipe. T
LeRoy Dreyfuss wrote: > mv.NET from BlueFinity would be using standard UniObjects and as > such, could not take advantage of connection pooling from U2 (CP). ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
