search

laforge49 / PAMailbox

0 stars 0 forks source link

We need some kind of CRON-like API #6

Open skunkiferous opened 11 years ago

skunkiferous commented 11 years ago

The discussion about timers reminded me of java.util.Timer. I think something like that is essential to an Actor API. Maybe we can extract it from Project Harmony, and turn it into one of our API classes?

laforge49 commented 11 years ago

Easy enough to write an actor to do it. I like to think of PAMailbox as a minimalist kernel, feature poor, fast and stable. CRON is a service, a part of an OS, but not a part of the kernel.

laforge49 commented 11 years ago

I think what we really need is a singleton actor which holds a set of Named (see PAUtil for Named) actors that provide various services. A CRON actor would be a first such service. All we really need is for MailboxFactory to hold that singleton, via an effectively final (set once) property. That's all the hook you need.

skunkiferous commented 11 years ago

Fair enough. But before I jump into implementing this, we need to work-out how those "Services" relate to OSGi Services (if at all).

laforge49 commented 11 years ago

not at all. they are just actors associated with an overarching service.

hmm. lets wait on this, I'm realizing that there may be different sets of actor services associated with different OSGI services. And I have a lot to do before diving into OSGI again.

On Thu, Apr 11, 2013 at 4:32 PM, Sebastien Diot notifications@github.comwrote:

Fair enough. But before I jump into implementing this, we need to work-out how those "Services" relate to OSGi Services (if at all).

— Reply to this email directly or view it on GitHubhttps://github.com/laforge49/PAMailbox/issues/6#issuecomment-16228176 .

laforge49 commented 11 years ago

CRON should be built over a database, I am thinking. This would be a lovely application for jfile, which I will be the next thing I migrate to the PActor API.