Voice over IP has been a hot subject for quite a while now, but till now we've never seen it being realised on big scale. First I think it has been marketised too much. Voice over ip is not rocket science. For me, it doesn't say more than 'telnet over ip'. Classic telephony calls are practicaly 100% reliable. TCP/IP connections are too unexpectuous: theres a big risk on delays, that are not important for data, but are so for voice. With TCP, you're sure your packets arrives, but it is too slow for voice packets. UDP hasn't this checking, is fast enough, but you are not sure the packets are delivered. How many times we like to see realaudio clips, but that we can't get a connection. Internet telephony is super for applications like netmeeting etc, but when somebody with a real telephone calls another , he expects that his call arrives, not that it is in a jam. People are used to this. So, in my opinion their will not be evolution to internet telephony as long their is no protocol redesign.
BUT, in most cases when using a pop3 account you have to go through your companies smtp server, or when accessing hotmail, you have to go through your companies proxy server. All these things can be logged, and in case of smtp, errors in emailadress can cause your mail to return to your companies admin.
has anybody noticed that they changed some indepth config params on the linux box? Maybe the reason for performance drop at 20 is an explanation for this. Can somebody explain what they did. -they forced the nic in full duplex -they set the Tag command queuing depth on the SCSI card to 24? -they adjusted the bdflush trigger
Slashdot Mirror
Well, at least Mickey can continue his job as mouse.
Cannabis resides in your hair for several months.
Voice over IP has been a hot subject for quite a while now, but till now we've never seen it being realised on big scale. First I think it has been marketised too much. Voice over ip is not rocket science. For me, it doesn't say more than 'telnet over ip'. Classic telephony calls are practicaly 100% reliable. TCP/IP connections are too unexpectuous: theres a big risk on delays, that are not important for data, but are so for voice. With TCP, you're sure your packets arrives, but it is too slow for voice packets. UDP hasn't this checking, is fast enough, but you are not sure the packets are delivered. How many times we like to see realaudio clips, but that we can't get a connection. Internet telephony is super for applications like netmeeting etc, but when somebody with a real telephone calls another , he expects that his call arrives, not that it is in a jam. People are used to this. So, in my opinion their will not be evolution to internet telephony as long their is no protocol redesign.
to find out the lifestyle behind the IP's they should download the whole internet, not ping ;-)
BUT, in most cases when using a pop3 account you have to go through your companies smtp server, or when accessing hotmail, you have to go through your companies proxy server. All these things can be logged, and in case of smtp, errors in emailadress can cause your mail to return to your companies admin.
has anybody noticed that they changed some indepth config params on the linux box? Maybe the reason for performance drop at 20 is an explanation for this. Can somebody explain what they did. -they forced the nic in full duplex -they set the Tag command queuing depth on the SCSI card to 24? -they adjusted the bdflush trigger