One notable addition: unlike pascal C++ is case sensitive. So you need to
match variable and function identifiers exactly which is not the case with
pascal code usually. For example:
procedure SetVariable(variable: boolean);
can be called in pascal as setvariable(variable); and this is legal
Hello all
I'm trying an HTTP-Get software but I found that UrlEncode (from IcsUrl.pas)
is not working according the protocol.
UrlEncode simply encodes all the URL without taking care of (parse)
Protocol, Folders, File and Data.
Example:
http : // user:[EMAIL PROTECTED] site .com:80/fol 1/fol
Hello:
The UrlEncode function is to encode strings to be included in URLs, by
escaping any invalid characters, not to encode complete URLs. You can
encode a complete URL, for example, when you want to send that URL as a
parameter in the QueryString, but this is not what you want to
- Original Message -
From: Francois PIETTE [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Sunday, February 12, 2006 7:23 AM
Subject: Re: [twsocket] Fast Pings ! - C++ :-(
I've seen in the usermade. But the code is in Delphi,
There is not much differences between
procedure = void?
function?
nil = NULL
TraceAddr: array [1..TraceMax] of string ; = string TraceAddr[TraceMax] with
first index = 1 ?
{$R *.DFM} ???
with Sender as TPingThread do ? we are assuming that all comes from
TPingThread ?
= !=
anyway, the problem is not so much to read the code
I already answer that question (or very similar) one or two days ago !
The answer was: UrlEncode is not to encode an URL but to encode a string to
be part of an URL, escaping unallowed charcaters in an URL. If you need to
parse an URL, use ParseUrl.
--
Contribute to the SSL Effort. Visit
anyway, the problem is not so much to read the code in Delphi, but to
see the form and its components (with ther properties).
You can open Delphi forms with BCB !
You can even copy/paste from Delphi form to BCB forms !!
--
Contribute to the SSL Effort. Visit
Thanks DZ-Jay. I think we need to add a more complete function, ..just what
to do if we need to encode (correctly) a full URL to use with HttpCli? ...It
was my problem the last week!!
I have hijacked, converted and shared a full URL encoder from Indy10.0.52
http://www.mcrenox.com.ar/uri.pas
I don't understand why you need such complex code for doing such simple task
as building an url !
It's just a matter of a few string concatenation and calling UrlEncode for
the parameters.
HttpCli1.URL := 'http://' + MyHostVar + '/' + MyPathVar + '?' +
'ParamName1=' +
Yes I know, but I'm meaning if we need to process an unknown URL entered by
user. May be we need a general URL encoder, capable to parse and encode each
part if necessary in a correct way.
thanks,
David
- Original Message -
From: Francois PIETTE [EMAIL PROTECTED]
To: ICS support
David A. G. wrote:
Thanks DZ-Jay. I think we need to add a more complete function, ..just what
to do if we need to encode (correctly) a full URL to use with HttpCli? ...It
was my problem the last week!!
That would make no sense. The encoder couldn't tell the difference
between real
The URL must be encoded because may have illegal characters:
The user may enter an URL like:
http://www.site.com/fol 1/fol 2/file 1.jpg?par=sdf|dfgó.jpg
This URL must be encoded as:
http://www.site.com/fol%201/fol%202/file%201.jpg?par=sdf%7Cdfg%F3.jpg
This kind of codification must be
You can use the PArseURL function to separate parts, then encode the path
and the parameters and merge with string concetanation.
Regards,
SZ
- Original Message -
From: David A. G. [EMAIL PROTECTED]
To: ICS support mailing twsocket@elists.org
Sent: Monday, February 13, 2006 5:15 AM
13 matches
Mail list logo