<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.6000.16544" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=687300915-18052011><FONT face=Arial color=#0000ff size=2>The
differences I mentioned are just the tip of the iceberg. Another example: the
RFC definition for URI permits for every scheme to define their own character
escape sequence for special and non ascii-characters. Guess what: sip allows
reserved characters in the user field :
sip:+1-212-555-1212:1234@gateway.com;user=phone. Another one?
sip:alice;day=tuesday@atlanta.com is allowed and means user="alice;day=tuesday".
(both from <A
href="http://tools.ietf.org/html/rfc3261#section-19.1.23">http://tools.ietf.org/html/rfc3261#section-19.1.23</A>)</FONT></SPAN></DIV>
<DIV><SPAN class=687300915-18052011><FONT><FONT face=Arial color=#0000ff
size=2>An "extra" field is not going to be enough to get around these
differences I'm afraid.</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV></FONT></SPAN><SPAN class=687300915-18052011><FONT face=Arial color=#0000ff
size=2>Ludo</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=fr dir=ltr align=left><FONT face=Tahoma
size=2>-----Message d'origine-----<BR><B>De :</B>
fpc-pascal-bounces@lists.freepascal.org
[mailto:fpc-pascal-bounces@lists.freepascal.org] <B>De la part de</B>
ik<BR><B>Envoyé :</B> mercredi 18 mai 2011 17:03<BR><B>À :</B>
FPC-Pascal users discussions<BR><B>Objet :</B> Re: RE : [fpc-pascal] Re:
URIParser<BR><BR></FONT></DIV>
<DIV dir=ltr>
<DIV class=gmail_quote>On Wed, May 18, 2011 at 17:56, <SPAN dir=ltr><<A
href="mailto:michael.vancanneyt@wisa.be">michael.vancanneyt@wisa.be</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV class=im><BR><BR>On Wed, 18 May 2011, Ludo Brands wrote:<BR><BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Problem
is that the RFC definition for the URI doesn't specify the<BR>individual
protocol scheme. So every protocol can specify it's own stuff.<BR><BR>Take
the general sip
URI:<BR>sip:user:password@host:port;uri-parameters?headers. User can be a
telephone<BR>number with folowing definition: global-phone-number =
"+"<BR>base-phone-number [isdn-subaddress]<BR>
[post-dial]
*(area-specifier /<BR>
service-provider /
future-extension)<BR>Or<BR>local-phone-number = 1*(phonedigit
/ dtmf-digit /<BR>
pause-character) [isdn-subaddress]<BR>
[post-dial]
area-specifier<BR>
*(area-specifier / service-provider /<BR>
future-extension)<BR>This definitely will require custom
processing.<BR>Also both uri-parameters and headers are name=value pairs.
The first are<BR>separated by ";" and the second by "&"...<BR><BR>I'm
afraid a universal URI decoder isn't
possible.<BR></BLOCKQUOTE><BR></DIV>Great. In that case I just declare that
URIParser will only work for ftp and http<BR>protocols :-)</BLOCKQUOTE>
<DIV><BR>I think it is possible. You can also add another field to the record
of "Extra data" and allow others to parse it.<BR>the headers are like the HTTP
URI (even the encoding of it is the same), and the params are like the HTTP
Post more or less but divided by a semicolon. But I can work with
parsing it myself imho, because that part is either starting with question
mark or by semicolon.<BR> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV></DIV>
<DIV class=h5><BR><BR>Michael.<BR></DIV></DIV></BLOCKQUOTE>
<DIV><BR>Ido<BR> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV class=h5>_______________________________________________<BR>fpc-pascal
maillist - <A href="mailto:fpc-pascal@lists.freepascal.org"
target=_blank>fpc-pascal@lists.freepascal.org</A><BR><A
href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal"
target=_blank>http://lists.freepascal.org/mailman/listinfo/fpc-pascal</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>