is libas-protocol closed source or open source? [answered]

in my day job i rely very very heavily on Exchange 2013 for my work (and Lync 2013). the current implementation on Jolla is a lacking for my purposes. i have to supplement it with Lync 2013 on Android and OWA, which is a bit of a pain.

i'm looking to write simple apps (maybe even CLI ones) to fill the gaps. i don't believe in reinventing the wheel so if libas-protocol is open sourced, that would already solve 80% of my problems as i can re-use it. unfortunately, it is not and that means i may be forced to go the route of something like EWS wrapper for python etc.

@droll - Unfortunately due to patents, open source implementations of Exchange can't be legally shipped in commercial mobile products, see this link for more info: http://www.microsoft.com/en-us/legal/intellectualproperty/IPLicensing/Programs/exchangeactivesyncprotocol.aspx

@VDVsx that's only in Jurisdictions that recognize algorithms/software as patentable. And even then it should be possible in most cases because of interoperability exceptions to patent law.

yeah, i'm familiar with the protocol and its licensing terms (from the principal). the google link is for something else. but many thanks for trying to help out.