Antonio Gallardo wrote:
Hi,
In the current model every component dveloper must take care of lookup()
and release() every resource it takes from the ComponentManager.
I think this is a bad practice. Why?
It remember me the old MS Windows days 3.0 (to at least Windows Me). When
a bad written applications (in the case of Cocoon, read component) can
hang all the system.
There is an analogy to the current model of Cocoon:
If your component "forget" release the resource it lookups before, then it
will start to "eat" all the memory and you will have soon or later an "Out
of Memory Error" and the need to restart the server. :-(
I propose to find another way to manage the componets and get away this
issue.
Why every component developer MUST lookup() and release(). I think the
lookup() is fine to define the components a component need. But the
release() must be done by the ComponentManager (Its my point of view).
For example, the ComponentManager must take care of what and when
"release" a resource.
I hope the above catch my point of view. Thanks for get this comment in
the correct way. I dont need to say that I still love Cocoon!
Autodecommissioning of components has been proposed for Avalon 5.0
--
Stefano Mazzocchi <[EMAIL PROTECTED]>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
