MSFT Internet Explorer vs. NSCP Navigator Message Board

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 : MSFT Internet Explorer vs. NSCP Navigator

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Daniel Schuh who wrote (20687)	9/13/1998 12:18:00 PM
From: rudedog	Read Replies (1) of 24154

Dan - When did Microsoft actually ship a TCP/IP Winsock for Windows 3? In 1989, I was lead designer on a team building a complex retail system which had an IBM S/390 for core transactions, a set of Sun (later HP) Unix boxes for relational database work (Sybase) which managed support and tracking data as well as real-time business rules, and a client system running Windows. The windows boxes used both HALAPI (to do CICS to the mainframe) and TCP/IP to talk to the Unix boxes. We used a stack from FTP for the TCP/IP stuff. This was a large system both in physical and geographic terms (used a WAN for stores in several states). MSFT was very interested in various parts of the work and sent engineering teams in at various times to work with us, and to try alternate designs using all MSFT technology. They put up a parallel system using OS/2 SQL Server which was tested in 1990. It included a MSFT-written TCP/IP stack over NDIS. Performance of this system was not too bad given that it was running on a 486-based server and the 'real' system was on a Sun 690. It did not have enough headroom to support the real system but the MSFT TCP/IP stack worked quite well. The MSFT team also put up an OS/2 system which managed the CICS traffic through a consolidator - IBM also helped out with that. This approach would have been much less costly than putting the HALAPI boards in every client and doing two WANs, one for SNA and a second for TCP/IP. So at least as far back as 1990, there was significant interest at the engineering level in a TCP/IP stack for MSFT. That work later rolled into both Windows and NT, but not for many years. Watch out for that DNA retrovirus. You know what DNA stands for of course - National Dyslexia Association... <GG>

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next