I have been prototyping a calendar server, and I am curious to hear people input on it:
My goal was to create a core set of services to manage calendar, addressbook, possibly todo's since most of the free and even major commercial calendar servers lack programmable API's to schedule events.
The implementation is based on JBoss and technologies that should be very similar to what you guys use. I got a couple of things working:
- Calendar/ Group schduleing.
- Live Ical export for integration with Mozilla Calendar.
- Templateable email notification of invitation and meeting changes.
I am working on:
- VCard, FBURL, VFreeBusy to allow some integration with Outlook and Evolution.
- LDAP replication of Address Book for OutLook and Mozilla (maybe Evolution).
I think with Mozilla Calendar and Mail it would be a viable solution.
The reason I write to you is because I was looking to integrate with a mail server for IMIP implementation. Haveing a hook to a mailserver would allow to implement IMIP scheduleing and intercept mail for processing. It would open the door to better interoperability with Evolution, and maybe Outlook(I read somewher it does some IMIP).
Also since the persistent state is centralized it could be exposed many other ways:
-to the mobile too via WAP, and syncML with Sync4j.
-CAP if somebody ever gets a free CAP client working.
I really think that having an open and functional backoffice server would allow integration of custom workflows and IT soultions with the desktop in a much more coherent way than it is done today.
So what you guys think?
the log4j sniplet I posted didn't come through all the way. I'll repost it on the wiki when I write the docs for mail services M1. This week I'm mostly testing, fixing bugs and writing docs (aka the dirty work). I'm counting on you guys to nail the few final issues.
i share the blame for propagating this mail log stuff (see my earlier forum post and cvs commits), sorry.
but would still be nice to treat conversational logging specially and be able to manage logging via jmx, as opposed to manually going in and redeploying log4j.xml. only way to treat conversational logging specially is to augment the simple Logger.getLogger(...) log4j factory with other factories that create client or server loggers. we have that option now from our mail log mbean.
so maybe what we need instead is a generic jmx interface to log4j then, and not just for jboss-mail? that would benefit the whole jboss platform as well.
That is an AWESOME idea.
thanks --- looks like someone halfway beat me to it though --- i'm looking in 3.2.4RC2, and there's an mbean called "jboss.system:service=Logging,type=Log4jService". folks can take a peek to see what it offers.
doesn't seem as fine-grained as what we're talking about, and rather seems to rely on redeployment of the log4j.xml configuration file for full manageability.
Lets put this off though. We need to focus on getting M1 out and planning for what goes in M2. I posted some ideas on the wiki (refined the planning). It is ambitious but we can revise it as needed.
absolutely. its in my to-do list at low priority, so it won't get touched till all our M1 stuff gets done.