Comments on: OpenDS, OpenID, and Atom — oh, my http://www.xmlgrrl.com/blog/archives/2007/05/07/opends-openid-and-atom-oh-my/ XML, identity, crafting, and other tangled musings Fri, 05 Sep 2008 15:06:56 +0000 http://wordpress.org/?v=2.5 By: Eve http://www.xmlgrrl.com/blog/archives/2007/05/07/opends-openid-and-atom-oh-my/#comment-64102 Eve Mon, 14 May 2007 00:08:38 +0000 http://www.xmlgrrl.com/blog/archives/2007/05/07/opends-openid-and-atom-oh-my/#comment-64102 Hey, glad to hear from you and glad you liked what you saw in the OpenDS/OpenID/APP combination! Hey, glad to hear from you and glad you liked what you saw in the OpenDS/OpenID/APP combination!

]]> By: M. David Peterson http://www.xmlgrrl.com/blog/archives/2007/05/07/opends-openid-and-atom-oh-my/#comment-64081 M. David Peterson Sun, 13 May 2007 21:17:07 +0000 http://www.xmlgrrl.com/blog/archives/2007/05/07/opends-openid-and-atom-oh-my/#comment-64081 Russ (Miles) was able to meet up with Trey several times at JavaONE and walked away *extremely* impressed. We have a test instance of the Heraldry OpenID server up and running at http://openid.name/ but from the sounds of it, we are going to be moving this Trey's OpenDS+OpenID+APP app just as soon as we can. We have our own in-house APP server (in fact, as of this morning, we now have two :D), which probably seems like overkill. Fact is, however, that each server has been built and optimized with a specific purpose. The fact that the interface is the same (from an API standpoint) means that we can make better re-use of our client code base by minimizing the amount of customization required for each specific purpose. With this in mind, we most certainly will be making use of this code base from the standpoint of customer profile management. Great stuff! Russ (Miles) was able to meet up with Trey several times at JavaONE and walked away *extremely* impressed. We have a test instance of the Heraldry OpenID server up and running at http://openid.name/ but from the sounds of it, we are going to be moving this Trey’s OpenDS+OpenID+APP app just as soon as we can. We have our own in-house APP server (in fact, as of this morning, we now have two :D), which probably seems like overkill. Fact is, however, that each server has been built and optimized with a specific purpose. The fact that the interface is the same (from an API standpoint) means that we can make better re-use of our client code base by minimizing the amount of customization required for each specific purpose. With this in mind, we most certainly will be making use of this code base from the standpoint of customer profile management.

Great stuff!

]]>