🚀 go-pugleaf

Yes, your right, but that is not the scenario I'm working with.  I am 
running pHTTP in multiple threads, am storing the parent URL to a table and 
coming back to it later to possibly analyze the links found in the HTML that 
I previously cached to a memo field.  What I am left with at that point is 
the Parent URL, Host(which in this case would seem to be no help) and the 
link information which may or may not be relative, or may be an external 
link.  I would rather combine the parent and link rather than tie up 
bandwidth making a second call to the parent to reestablish a path with the 
server.

Played with the ProcessPath a little bit and it doesn't seem to be a 
complete solution, but does get me halfway there.  It doesn't recognize 
external links and simply appends them to the parent link:

ProcessPath("http://www.widgets.com/products.html", 
"http"//www.anotherwidget.com/html", "/"); will combine as 
"http://www.widgets.com/products.html/http:/www.anotherwidget.com/html"

.  It does seem to take care of all that nasty relative stuff that occurs 
within the host however.  So I should only need to determine whether or not 
it's an external link and move on.

Thanks
Ted




"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4200085b$1@newsgroups.borland.com...
>
> "Ted Tripp" <ttripp@rankexec.com> wrote in message
> news:4200074a$1@newsgroups.borland.com...
>
>> the asLink would be on whatever the current document page is,
>> asCurrentURL, in other words the address you would find in internet
>> explorer when looking at the link on a page.
>
> The browser will already handle qualifying the path BEFORE sending it to 
> the
> HTTP server.  The browser knows what its current URL is and what URL is
> being requested.  The requests that are sent to the HTTP server are 
> already
> qualified to begin with.
>
>
> Gambit
>
>