Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Inktomi (INKT) -- Ignore unavailable to you. Want to Upgrade?

To: shag007 who wrote (124)	7/1/1998 6:17:00 PM
From: Jerry Whlan	Respond to of 1945

Paul Gauthier says there's a very simple solution to the problem. I hope this is true. If the whole idea of their traffic server is to use cache to speed up access time and free up bandwidth then they should have gone over this problem with Digex. I would like to here some follow up on this situation to see if the problem was solved in a timely matter. I do not know about the incident in question, but having interviewed with INKT I am generally familiar with how the traffic server is implemented and the details of the story ring true to me. I believe that the fix to this particular problem is trivial, essentially, Digex need only configure their system to allow requests to cybercash and other similarly sensitive web sites to go directly to the web-site rather than be redirected through the traffic server system. It shouldn't be hard to do as long as the cpus in the routers are fast enough. My read of the story is that it was a simple case of pilot error, either Digex ignored the details (that's where the devil is) of the traffic server implementation, or INKT neglected to communicate those details to Digex. Either way, I would be surprised if the problem weren't fixed within a day of Digex taking it seriously.