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 : George Gilder - Forbes ASAP -- Ignore unavailable to you. Want to Upgrade?

To: Martin Atogho who wrote (2970)	2/29/2000 12:17:00 PM
From: Scott C. Lemon	Read Replies (1) \| Respond to of 5853

Hello Martin, > I believe Xla has a few patents, but I don't understand > the sector well enough to tell whether it would offer > them the opportunity for royalties if ISLD or AKAM wanted > to adopt their approach to storewidth. There are some patents being applied for in this space that I am aware of, but the basic "cache to cache" transfer protocols are already public standards. (i.e. HTTP, FTP, RTSP, RTP, etc.) The ICP protocols, which are used for locating cached content are also standard. I searched the patent databases and don't seem to be able to find any ... if you know of any patent numbers, they would be interesting to look at ... There are two areas that I have heard/seen patent activity. 1) The automatic redirection of end-users browsers to the "approriate" cache. There are capabilities in a users browser to configure the use of a cache. But in the case of large distributed caches, when a user goes to visit a web site, they must be transparently redirected to request content from the "closest" or "most appropriate" cache. That way a user in the eastern US is requesting pages and images from a cache in the eastern US ... while a user in eastern Europe is requesting content from a cache in eastern Europe. In both cases the users would have typed the same web site URL. 2) The "pre-filling" of caches based on end-users access patterns. There are a variety of ways to "cache" the content. The "easiest" is to do so on demand. This is the "default" way for the caches to be filled. If my browser asks for the CNN web site, it is pulled into cache at that time. All users who reques the site after me would get the cached copy which I pulled into cache. (Forget for now the issues with dated information ... let's say that's already solved) But if day after day, the cache owner realizes that I, and numerous other people, are always requesting the CNN web site, then they might go to CNN and sell them some software which will automatically "push" new pages to the caches when they are changed by CNN. This would then "pre-load" or "pre-fill" the cache with content that seems to be in demand. Both of these areas are still in heavy research, and there area number of different solutions that have been developed and implemented ... > Is this the case, or are the patents not applicable here? In these two areas, I do believe that there are patents being submitted ... Scott C. Lemon