Results for "Author: dan violet sagmiller"

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.

In All the other methods I've tried, I run into a barrier(around 170K+) where loading a file suddenly becomes very slow. I've tried many methods found here and in books, and none have proven to work as well as I was looking for. After a long search I ended up spending some off-time figuring a way out myself. This is what I came up with.(speed increases from 20 seconds@170k to .4 seconds@170k)

This gives a complete, Error-Correcting, Client and server to demonstrate communications via winsock. You may substitute the CLient program for any Telnet application. The telnet Server has only 22 lines of code, which does include error correction for any text based connections. The Client App has only 28 lines of code, with complete commenting and explataions for why errors arise, not just that they do show up.