How solid does this need to be prior to getting submitted back? Is there a referred source code repo to use (Sourceforge, code.google.com, ...)? The code still has some warts in it and wants some thought on things like where credentials get cached and such. Also need an open OAuth API to build against for the server side (Client doesn't need that). -bill > -----Original Message----- > From: Alexey Melnikov [mailto:alexey.melnikov@xxxxxxxxx] > Sent: Friday, July 16, 2010 4:08 PM > To: William Mills > Cc: cyrus-sasl@xxxxxxxxxxxxxxxxxxxx > Subject: Re: OAuth mechanism. > > William Mills wrote: > > > Hi, > > Hi William, > > > I'm writing a SASL mechanism for OAuth as a reference > impelementation. > > Is that somethign that would get submitted back into the > core of Cyrus > > SASL or shoudl it live as a separate entity. If it's a separate > > entity, are there other such opensource examples I can use > as a bassis > > for my packaging so I'm being consistent? > > This sounds interesting enough, so I think it can be > committed to Cyrus SASL itself. Which specification are you > planning to implement? > > Best Regards, > Alexey > >
