# Re: URCs and URL resolution

Michael Mealling (Michael.Mealling@oit.gatech.edu)
Wed, 28 Sep 1994 14:58:10 -0400 (EDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Keith Moore: "Re: URCs and URL resolution"
- Previous message: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- In reply to: Reed Wade: "URCs and URL resolution"
- Next in thread: Paul Francis: "Re: URCs and URL resolution"

    From: Michael.Mealling@oit.gatech.edu (Michael Mealling)

    Message-Id: <199409281858.OAA10005@oit.gatech.edu>

    Subject: Re: URCs and URL resolution

    To: wade@cs.utk.edu (Reed Wade)

    Date: Wed, 28 Sep 1994 14:58:10 -0400 (EDT)

    In-Reply-To: <9409281443.AA16231@honk.cs.utk.edu> from "Reed Wade" at Sep 28, 94 10:43:39 am

Reed Wade said this:
> One would be a full URC (or URC-like thing) with lots of
> handy info which you might get via a whois++ search or
> related lookup.
>
> The other--for URL resolution would use a very lightweight
> RPC or RPC-like mechanism.

I've been toying with a lightweight version of whois++ that is basically
a stripped version of the protocol that runs under udp. It has no support
for the HOLD constraint and doesn't support centroids or fancy return
types. So basically your UDP packet would contain:

template=URC;URN=bla:match=exact

And your returned URC would be contained in one or more returned packets.

Now, I don't know that much about UDP so I wouldn't know how to handle
multiple returned packets if the URC you returned was overly large.
I could imagine limited the URC to only 5 or 6 fields with a limit on
the number of hits as in:

template=URC;URN=bla:match=exact:include=URN,URL,Content-Type,Content-Length:maxhits=1

so that it 'should' fit on one returned UDP packet.....

-MM

    --
    ------------------------------------------------------------------------------
    <HR><A HREF="http://www.gatech.edu/michael.html">
    <ADDRESS>Michael Mealling</ADDRESS>
    <ADDRESS>michael.mealling@oit.gatech.edu</ADDRESS></A>

- Next message: Keith Moore: "Re: URCs and URL resolution"
- Previous message: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- In reply to: Reed Wade: "URCs and URL resolution"
- Next in thread: Paul Francis: "Re: URCs and URL resolution"