I think the real stuff is in the client (disclaimer: my employer does this), as organizations aren't going to move to _replace_ Exchange. Anyone enterprise small enough would likely use a different server (and protocol) altogether anyway.
For my company, it is a matter of cost. Our hoster charges for bandwidth and disk. Email traffic contributes a large part of our total bandwidth. We can keep costs down by using GMail for mail and associated storage while our cost is used strictly for hosted files and websites.
This topic will inevitably go to the "it's not Firefox, it's the extensions" canned memory-hog statement. I would be perfectly happy with an Extension Monitor that tells me the resources extensions are actually taking. Then we can finally point some fingers in true slashdot style!
(Disclaimer, I have never searched for such a thing, nor am I interested in writing one)
If it was easy enough to implement new protocols, it would be exciting to do development. For example, if there were some XPCOM components that I could implement to talk to Exchange, that would be GREAT!
... give RedHat an instant "in" on the application server market so coveted by BEA and IBM? This seems like it could be an intersting fit, and would certainly save JBoss from extinction by Oracle (as seems to be the trend).
Slashdot Mirror
I think the real stuff is in the client (disclaimer: my employer does this), as organizations aren't going to move to _replace_ Exchange. Anyone enterprise small enough would likely use a different server (and protocol) altogether anyway.
Just my $0.02.
For my company, it is a matter of cost. Our hoster charges for bandwidth and disk. Email traffic contributes a large part of our total bandwidth. We can keep costs down by using GMail for mail and associated storage while our cost is used strictly for hosted files and websites.
If your company uses Exchange, I recommend Moonrug. They write Exchange/MAPI from Java and their stuff is very inexpensive (and fully supported).
This topic will inevitably go to the "it's not Firefox, it's the extensions" canned memory-hog statement. I would be perfectly happy with an Extension Monitor that tells me the resources extensions are actually taking. Then we can finally point some fingers in true slashdot style!
(Disclaimer, I have never searched for such a thing, nor am I interested in writing one)
If it was easy enough to implement new protocols, it would be exciting to do development. For example, if there were some XPCOM components that I could implement to talk to Exchange, that would be GREAT!
If such a thing does exist, please speak up!
In other news, Slashdot is now blocked by the great Firewall of China for suggestions that citizens leave the country.
Ah, the old days. Relive all the craziness at once.
... give RedHat an instant "in" on the application server market so coveted by BEA and IBM? This seems like it could be an intersting fit, and would certainly save JBoss from extinction by Oracle (as seems to be the trend).