Changeset 20643 in project


Ignore:
Timestamp:
10/04/10 15:23:13 (9 years ago)
Author:
sjamaan
Message:

Move down the uri-common->uri-generic conversion procedures to make them less prominently visible right at the top of the docs

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/eggref/4/uri-common

    r20642 r20643  
    9090Is the {{URI}}'s port the default port for the {{URI}}'s scheme?
    9191
    92 ==== uri-generic, string and list representation
    93 
    94 <procedure>(uri->uri-generic uri-common) => uri-generic</procedure><br>
    95 <procedure>(uri-generic->uri uri-common) => uri-common</procedure>
    96 
    97 To convert between uri-generic and uri-common objects, use these
    98 procedures.  As stated above, this will allow you to retrieve the
    99 original encoding of the URI components, but once you update a
    100 component from the uri-common side, the original encoding is no longer
    101 available (the updated value replaces the original value).
    102 
    103 <procedure>(uri->string uri-common [userinfo]) => string</procedure>
    104 
    105 Reconstructs the given URI into a string; uses a supplied function
    106 {{LAMBDA USERNAME PASSWORD -> STRING}} to map the userinfo part of the
    107 URI.  If not given, it represents the userinfo as the username followed
    108 by {{":******"}}.
    109 
    110 <procedure>(uri->list URI USERINFO) => LIST</procedure>
    111 
    112 Returns a list of the form {{(SCHEME SPECIFIC FRAGMENT)}};
    113 {{SPECIFIC}} is of the form {{(AUTHORITY PATH QUERY)}}.
    114 
    115 
    11692==== Accessors
    11793
     
    222198URI path segment normalization (RFC 3986 section 6.2.2.3)
    223199
     200==== uri-generic, string and list representation
     201
     202<procedure>(uri->uri-generic uri-common) => uri-generic</procedure><br>
     203<procedure>(uri-generic->uri uri-common) => uri-common</procedure>
     204
     205To convert between uri-generic and uri-common objects, use these
     206procedures.  As stated above, this will allow you to retrieve the
     207original encoding of the URI components, but once you update a
     208component from the uri-common side, the original encoding is no longer
     209available (the updated value replaces the original value).
     210
     211<procedure>(uri->string uri-common [userinfo]) => string</procedure>
     212
     213Reconstructs the given URI into a string; uses a supplied function
     214{{LAMBDA USERNAME PASSWORD -> STRING}} to map the userinfo part of the
     215URI.  If not given, it represents the userinfo as the username followed
     216by {{":******"}}.
     217
     218<procedure>(uri->list URI USERINFO) => LIST</procedure>
     219
     220Returns a list of the form {{(SCHEME SPECIFIC FRAGMENT)}};
     221{{SPECIFIC}} is of the form {{(AUTHORITY PATH QUERY)}}.
    224222
    225223=== Requires
Note: See TracChangeset for help on using the changeset viewer.