Considering there is no session pooling mechanism, every time you
connect to the back end you have to go through the login process,
which is a very expensive process time-wise. If you're sure the issue
is specifically with opening a file after you've already gone through
the connection, then I apologize that I have nothing of value to
offer.
I'm not too familiar with the internals here but it seems to me that
UO.NET is really just a PInvoke wrapper around unmanaged UO, so you
just have an extra layer to go through, which may explain a small
extra delay.
Note that PDP.NET and mv.NET do have session pooling, so most
operations are much faster.
Please feel free to contact me about sales and development services
for these products.
Good luck,
Tony
TG@ removethisNebula-RnD
..com
niall.twomey (AT) ie (DOT) flextronics.com wrote:
Quote:
I'm upgrading from Uniobjects to UO.NET but and have found one major
speed problem when opening Universe files on the backend server
In Uniobjects
Session.OpenFile(FileName)
In Uniobjects .Net
Session.CreateUniFile(FileName)
Session.CreateUnifile is much much slower than Session.Openfile.
Has anyone else experienced this, Is there a workaround to this ?
Thanks
Niall |