[Mono-osx] patch: Mac OS X keychain API additions

Leszek Wong leszekw at ololaiki.com
Fri Feb 4 19:59:52 EST 2011

I'm merely pointing to the fact that we may have hit the ceiling with the approach of extending the API, in regard to keychain APIs.
For example - single keychain on iOS (for a given app) which suggests a "static" KeyChain class and multiple keychains for MacOS which suggest "non-static" KeyChain class 
with bunch of operations of creating, deleting, enumerating, modifying etc these keychains which are MacOS -only.

As I see it, we have the following options:
- change the existing API (static Keychain -> non-static Keychain). Most likely not possible because it will break monotouch customers.
- don't implement the MacOS functionality which requires API change. This would be sad because the functionality seems to be rich and useful for MacOS programmers.
- holistically depart from the common Keychain code base and ensure the best coverage for iOS and MacOS. We'll keep the common functionality within #maccore and implement delta functionality in #monomac

Am I missing any other option?

On Feb 4, 2011, at 3:09 PM, Miguel de Icaza wrote:

> Hello
>> Does this make any sense?
> It does, but it does not prevent us from extending the existing API that
> exists so that it covers both.

More information about the Mono-osx mailing list