[Dev] Started a Simple Resolver in PHP....

[Markus Sabadello]

Hi Nika,

This is cool.. Are you running your resolver at some public location where
we can see it?

By the way, the latest version of the XRI resolution specification is here:
http://docs.oasis-open.org/xri/2.0/specs/cd02/xri-resolution-V2.0-cd-02.pdf

You should use this for your reference.

Maybe I can try to clarify a few points..

1) You should especially look at section 9.1.10 (Construction of the Next
Authority URI). This explains what requests are sent to your authority
resolution server when an XRI resolver tries to resolve an XRI.
2) Normally you don't want to directly produce XRD documents for top-level
i-names such as =test. These i-names are registered and resolved by the GRS
(Global Registry Services). However, what you definitely can do is resolve
COMMUNITY i-names UNDER these top-level i-names. For example, if you own the
i-name =test, then you can point its authority resolution SEP (service
endpoint) to your own authority resolution server, which can then resolve
community i-names such as =test*test1, =test*test2, =test*test3, etc... If
your server is running at http://example.com/resolver.php, then it will
receive requests like http://example.com/resolver.php/*test1,
http://example.com/resolver.php/*test2, and it is expected to produce
correct XRDs for these community i-names.
3) As I also wrote in my other mail, the Query element just contains a
single subsegment (the one that produced the current XRD), not the whole
identifier. For example *test1, *test2, etc...

Hope this makes some sense......

Markus

On 1/28/08, Nika Jones <njones at ouno.com> wrote:
>
>  Hello,
>
>
> I've gotten a simple resolver built in PHP... you can pass in a URL like
>
>
> http://example.com/resolver.php/=test
>
>
> And it will using a flat file or SQLite pull back something like
>
>
>  <XRDS ref="xri://test" xmlns="xri://$xrds">  <XRD xmlns="xri://$xrd*($v*
> 2.0)">  <Query>=test</Query>  <Status code="100"/>
> <Expires>2008-01-28T10:18:01.0800Z</Expires>
> <ProviderID>xri://=</ProviderID>  <LocalID
> priority="10">!7A49.7EDD.2592.F77B</LocalID>  <CanonicalID
> priority="10">=!7A49.7EDD.2592.F77B</CanonicalID>  <Service>  <Type
> select="true">xri://$res*auth*($v*2.0)</Type>
> <MediaType>application/xrds+xml;trust=none</MediaType>  <URI>
> http://example.com/resolver.php/=test/</URI>  </Service>  </XRD> </XRDS>
>
>
> Note: the CanonicalID and LocalID's are hard coded for now...
>
>
> However I'm not sure what to do with something like
>
>
> http://example.com/resolver.php/=test/*foo
>
>
> Is the *foo supposed to be on another server? and looked up as per the
> spec "Select Next authority resolution service endpoint (see text)" in the
> flow chart on page 24 of the xri-resolution-v2.0-wd-10.pdf?
>
> Thanks in advanced.
>
> Nika
>
> ----
> NOTE: I sent this originally to the openxri-users at lists.sourceforge.netlist, but I didn't have a
> postmaster at ouno.com set up so the mail was rejected... and it seems that
> it could be rejected for the day... so I've sent it here in hopes of someone
> forwarding it to the openxri list, however my next emails should be on the
> openxri list (as I've set up the required postmaster account). Thanks. Nika
>
> _______________________________________________
> Dev mailing list
> Dev at inames.net
> http://dev.inames.net/mailman/listinfo/dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://dev.inames.net/pipermail/dev/attachments/20080129/6fd5b71f/attachment.html