Jason,
> I was trying to write a high-level implementation so I didn't have to
> care about the underlying storage, but I think on balance you're
> correct. The performance would suck :-(
High-level doesn't mean building on (too) low-level primitives. You want
the ability to allow to subsystems that can do things efficiently. You need
to be a framework for them to use, not the otherway around.
For example, lets say that you want a report of who has messages waiting,
how many, and how big are the mailboxes? You can either do a lot of work,
or you can allow a JDBC repository to execute:
select count(*) as MessagesWaiting,
sum(length(message_body)) as MailBoxSize,
repository_name as User
from inbox
group by repository_name;
Mind you, we should distinguish between reports such as this, and data
gathering, e.g., a connection counter. But this does illustrate why you
would want each subsystem to play an active role, and register its
capabilities. Are you familar with the /proc system in linux?
I'll respond to everything else later when I've some time.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
