<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>RE: XRI Python stub resolver</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Gabe,<BR>
Glad to see code shaping up for this! It seems to me that OpenXRI would be the best place for it right now.<BR>
<BR>
--David<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: general-bounces@openid.net on behalf of Gabe Wachob<BR>
Sent: Mon 9/4/2006 3:56 PM<BR>
To: xri@lists.oasis-open.org; iss-comment@lists.xdi.org; i-broker-discuss@lists.xdi.org; general@openid.net<BR>
Subject: XRI Python stub resolver<BR>
<BR>
I just put together some Python code to do XRI resolution against XRI<BR>
proxies. In particular, it seems to be working fine with the xri.net proxy<BR>
(though my code does exercise the service selection proxy functionality that<BR>
xri.net doesn't seem to be doing correctly right now).<BR>
<BR>
<BR>
<BR>
Its very alpha or pre-alpha, but I wanted to get XRI usage enabled for all<BR>
the Pythonistas out there. I don't quite know where this code should live<BR>
(openxri? heraldry? wiki?)<BR>
<BR>
<BR>
<BR>
<A HREF="http://wiki.oasis-open.org/xri/PythonCode">http://wiki.oasis-open.org/xri/PythonCode</A><BR>
<BR>
<BR>
<BR>
Please send comments/questions directly to me as this email is heavily<BR>
cross-posted.<BR>
<BR>
<BR>
<BR>
-Gabe<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>