Hi Dav,
You may wish to look into MSMQ helps handle large bursts of web traffic as
long as immediate answers and actions aren't required. And do please
consider MTS for application-level transactions, MTS can help prevent a
disconnect between what you promise in the forms and what actually happens
in the backend. COM+ bundles both and they are exposed using
EnterpriseServices namespace in .NET Framework. These services come free
with most if not all modern Microsoft OSes.
Best personal regards,
-- Li-fan
--
Li-fan Chen
Software analyst/developer, Entrepreneur
Markham, Ontario, Canada
"Dav" <mu**********@yahoo.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
From what I know you can use com+ in asp.net via interop. If I convert
these com+ objects to .NET (VB.NET) do I still need MTS or does the
.NET framework handle the object pooling and other features of MTS? So,
instead of a bunch of COM+ objects on MTS that my asp.net can
reference, can I convert them to .NET DLLs and just keep them in the
bin folder?
Basically, if I convert my COM+ objects to .NET do I need MTS for a
high traffic site?
If you can post any thoughts, experiences or links, that would be
appreciated.
Thanks!