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.

SI - Site Forums : Silicon Investor - Welcome New SI Members! -- Ignore unavailable to you. Want to Upgrade?

To: SI Brad who wrote (425)	2/7/1998 8:27:00 PM
From: Barry Grossman	Read Replies (2) \| Respond to of 32871

Brad, I think the charts capability on SI is great but I have several suggestions for additional utility. 1. Capability of comparing any NYSE, NASDAQ & ASE stocks instead of just the selected tech stocks. Many of us have non-tech stocks in our portfolios and it would be a real benefit to be able to compare them on the same chart with our tech holdings. I don't know how how you get the data for the charts but if you can utilize data for some stocks, why not others? 2. Instead of preselected time periods, 20 days, 30 days, 40 days, etc. - the ability to personally choose the specific time period would be very nifty. Would this ever be a possibility? Barry

To: SI Brad who wrote (425)	2/8/1998 7:57:00 PM
From: Spots	Respond to of 32871

>>Oh no, now someone is going to ask, "what is a traceroute"? Hopefully someone else will be able to explain it :) Ok, Brad. A tracerout is a way of tracking how IP packets get routed. There's a TCPIP utility on virtually any host (Windows, Unix, Netware) called TRACERT or similar which allows you to enter a target server and get back the packet routing to get to that server from your system (given whatever routing tables are in effect at the moment, which can change). It works as follows: The utility first sends out a packet with a Time To Kill field of 1. Every routing hop the packet goes through decrements the TTK field by 1, and if it gets to zero the router refuses to forward it and returns it with its (the router's) IP address. So TRACERT sends out a TTK 1 packet and it either gets delivered or returned with a router's IP address. Then it sends out a TTK 2 packet, which either get's delivered or returned with the next router's IP address. This continues till the packet gets delivered, at which point TRACERT knows all the IP addresses of the hops to get to the destination. BTW, "router" can be a router or any IP node which does IP forwarding (but not a bridge or repeater; these guys don't operate at the IP protocol level--they're lower down and don't understand IP addresses). Sneaky, no? Remember this the next time you accept a cookie. All kinds of stuff can be inferred from the most innocent- sounding protocols ... Ok, Brad? :) Regards, Spots