dotnet distributed apps: WellKnown Single Call Objects and Enterprise Services -- dotnet distributed apps

Re: WellKnown Single Call Objects and Enterprise Services

Sam Santiago
12/27/2004 8:44:26 PM

COM+ is most likely controlling the lifetime of your object. Does the =
object ever terminate? Checkout the Advanced and Pooling and Recycling =
tabs on the properties of your COM+ application.

You might also want to check out this article:

..NET Remoting Architectural Assessment
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/dndotn=
et/html/dotnetremotearch.asp

Here's an excerpt:

"Building COM+ integration directly on top of Remoting is certainly =
possible, then, and does offer the obvious benefits provided by =
Enterprise Services=E2=80=94for example, object pooling, distributed =
transaction support, and role-based security. Missing, though, are good =
examples of how to do this and how such an approach stacks up =
architecturally with respect to future proofing. It would be reasonable =
to expect that the COM+ context infrastructure and the Remoting context =
infrastructure will come closer together over time. Precisely when or =
how this will happen is unclear at this stage."

Thanks,

Sam

--=20
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________
"Mehdi Mirzaie" <MehdiMirzaie@discussions.microsoft.com> wrote in =
message news:D9176D6D-A8E3-402B-A47C-66AC6AA072EA@microsoft.com...
[quoted text, click to view]

Re: WellKnown Single Call Objects and Enterprise Services

Mehdi Mirzaie
12/30/2004 2:33:02 PM

Hi there
COM+ Objects ( Server Activation [ server context ]) will be terminated (
Disposed) when u call Dipose method explicitly for them , but i can use
activation-deactivation technique with AutoComplete attribute to deactivate
them ( AutoComplete attribute is usually used for transactional objects
methods , here is an exception) but it is not enough for me , because objects
are alive , and use resources.
Application Pooling and Recycling are new for Win2003 and XP and they are
for COM+ Applications not COM+ Objects .
i dont know why Remoting dont call Dispose method implicitly for these
objects , but it calls dipose methods for other types objects. :(
if it doesnt work correclty (Remoting Singleton with Enterprise Services for
disposing) i have to write a wrapper class for my Com+ Objects to call
dispose method explicitly after each method call like an Interceptor Filter .

[quoted text, click to view]

Re: WellKnown Single Call Objects and Enterprise Services

Ed
2/11/2005 4:02:41 PM

Object with [AutoComplete] methods are deactivated immediately after call to
those methods (regardless IDisposable). But if pooling is enabled, object
simply returns to pool (and continues using resources). Dispose() call
releases only COM+ context (and actually gets object from pool in order to
do that (for ServerActivated)). Try this: apply AutoComplete attribute but
set ObjectPooling(false) (if only you do not use transactions).

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet distributed apps group.