a solution that will work in
our current situation, but is there a better way?
Thanks,
Paul
-Original Message-
From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 4:38 PM
To: CF-Talk
Subject: RE: Looping 600 CFHTTP requests - Performance
Paul
I understand better
Paul
I don't think I understand what you are doing... unless you are
dealing with one-of-a-kind items.
As I understand it:
You send the affiliate a feed of all all your in stock items...
what's a feed SKU qty?
Some time passes and the affiliate updates their site
Now the affiliate wants
to track the number of dead links
to find out if we have a major or minor problem.
What would be the most efficient way to do this?
-Original Message-
From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 10:57 AM
To: CF-Talk
Subject: Re: Looping 600 CFHTTP requests
Paul Sizemore wrote:
What would be the most efficient way to do this?
What about parsing your web logs for server errors? You can use a log
analysis program (like Analog) or even write your own to do this
--
If it ain't broke, it doesn't have enough features yet.
email:
Paul
I understand better, but still not completely.
Why are the links dead... do you delete the product page when an item
goes out of stock.
As I understand it, these are links from AOL to to your pages,
furnished by you.
Therefore you have control over whether a link is dead... you make it
5 matches
Mail list logo
