Do we need a new provider for every version of SmarterMail?

Question

I was asked some time back by our friends at Microsoft to contribute my changes for SmarterMail 7/8/9 back to the community.  I'm looking through the code and I'm questioning if we need a provider for every version. I think we would only need a new provider when there's a massive change to the API and only then.

Thoughts?

I'll have my changes compiled into a separate build and sent up to the codeplex site by the weekend. I'm going to modify the SmarterMail7 provider to be the SmarterMail 7.x - 9.x provider and upload it as such (mostly because that's all the code skills that I have) but also because I believe it keeps thing simplier. 

 

BTW, I'm ecstatic to see Feodor involved in the project again.  

Answer 1

We just removed the check. It is stupidly annoying.

I really don't see a need for a new / separate library. The SM API hasn't changed in many many versions...

Answer 2

I strongly second this, ST has stated clearly that API is compatible through versions, so it's best to add a generic check for SM 7+.

I'd like to check your code when you upload it because I'm also working on my spare time on extending the SM provider. The problem I'm fixing is inheriting domain defaults, which I described here:

http://social.msdn.microsoft.com/Forums/en-US/wspsupport/thread/79649ba4-7147-4bbf-be33-ea081c59ad1a

Regards.

Answer 3

Has anyone approached SmarterTools about contributing to the SmarterMail provider as it is in their vested interest to do so?

Answer 4

I have personally tried to encourage them to take over this side of the project and to make the integration with WebsitePanel be their 'reference architecture' for other control panel vendors to reference when integration their own system.  I've had no luck but then I'm only one voice. If more of us were to do this, I'm sure they would step in.  They're a great bunch of guys and would be happy to help, I'm certain.

 

Jess

Answer 5

I was asked some time back by our friends at Microsoft to contribute my changes for SmarterMail 7/8/9 back to the community.  I'm looking through the code and I'm questioning if we need a provider for every version. I think we would only need a new provider when there's a massive change to the API and only then.

Thoughts?

This is probably good idea but how about features which SmarterMail dev team is adding every new SmarterMail version (like ActiveSync in SM8 and Jabber or EWS in SM9)? Are you planning to enable them (actually mentioned ActiveSync should not be enabled by default for all since it is being licenses by mailbox) by default?

Answer 6

Then as new features come out a new provider would be added or the provider updated.  I don't plan to enable any of these features Webio and honestly it's beyond my abilities. 

Jess