The difference is that you can change the ASO on the fly ... just
create a new instance and store it into a property that is injecting
the ASO itself.
On 12/18/05, Martin Strand <[EMAIL PROTECTED]> wrote:
> I'm still not sure I get it... Can't I just use a Hivemind service as if
> it were an ASO?
I'm still not sure I get it... Can't I just use a Hivemind service as if
it were an ASO? As I understand it, the service object is only created
once, so any changes I make to it will be visible to any part of my app
that uses that same service, right?
Or perhaps ASOs are distributed in a clus
If your object is there to maintain the state of the application, then
its an ASO, if its there to give a service (do something with method
arguments, or without them) then its a service...
Technically AFAIK you can differ them also in that an ASO is a
standalone, whereas a service may depend
Hi. :)
I want a Settings class to be visible to most parts of my app and I find
one thing somewhat confusing... Could someone please explain what the
difference is between a HiveMind service and an ASO with
scope="application"?
Thanks,
Martin
--
