Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version

Use of free SocketPro package for creating super client and server applications

, 23 Feb 2002
A set of socket libraries for writing distributed computing applications over the internet
socketpro.zip
netdemo
ClientComponents
MultiSvsSample
SvrComponents
bin
include
lib
Samples
client
DnsSvs
GetHTML
InternetIO
MultiSvsSample
SpeedTest
res
DResolver
Svr
NormalApp
NTSvs
help
trash
SecureSocket
SafeSocket
DNSResolver.exe
GetHtml.exe
IONet.exe
MultipleSvs.exe
MultiSvs.exe
MultiSvsClient.exe
NetBaseR.dll
SafeSocket.exe
SecureSocket.exe
SpeedTest.exe
ClientSocket.dll
DResolver.dll
SBroker.dll
SockFile.dll
fundamental.gif
patterns.gif
NetBaseR.lib
DNSResolver
DNSResolver.vbp
DNSResolver.vbw
frmDNSResolver.frm
frmDNSResolver.frx
frmChatClient.frm
frmChatClient.frx
GETHTML.vbp
GETHTML.vbw
iIO.frm
IONet
IONet.vbp
IONet.vbw
frmMultiSvs.frm
frmMultiSvs.frx
MultiSvs.vbp
MultiSvs.vbw
SafeSocket.vbp
SafeSocket.vbw
SecureSocket.frm
SpeedTest.ico
SpeedTest.aps
SpeedTest.clw
SpeedTest.dsp
SpeedTest.dsw
dlldata.obj
DNS.rgs
DResolver.aps
DResolver.def
DResolver.dsp
DResolver.dsw
DResolver.opt
DResolver.plg
DResolver.tlb
DResolverps.def
DResolverps.exp
DResolverps.lib
DResolverps.mk
DResolver_i.obj
DResolver_p.obj
MultipleSvs.dsp
MultipleSvs.dsw
MultiSvs.dsp
MultiSvs.dsw
MultiSvs.rgs
MultiSvs.tlb
MultiSvsps.def
MultiSvsps.mk
dlldata.obj
SafeSocket.aps
SafeSocket.dsp
SafeSocket.dsw
SafeSocket.plg
SafeSocket.rgs
SafeSocket.tlb
SafeSocketps.def
SafeSocketps.dll
SafeSocketps.exp
SafeSocketps.lib
SafeSocketps.mk
SafeSocket_i.obj
SafeSocket_p.obj
SPassword.rgs
MultipleSvs.exe
MultiSvs.exe
NetBaseR.dll
SafeSocket.exe
<html>

<head>
<meta name="GENERATOR" content="Microsoft FrontPage 3.0">
<title>Offset weaknesses of DCOM with strong points of socket</title>
</head>

<body>

<h3 align="center"><strong>Offset weaknesses of DCOM with strong points of socket</strong></h3>

<ol>
  <li>Introduction<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A few years ago when using DCOM to write simple
    distributed applications, I was fascinated with DCOM. However, I started to doubt this
    technology soon, and was gradually disappointed with it. Recently, I have time to work
    with socket. After diagnosing DCOM net data communication with net tools, and comparing it
    with socket, I found that DCOM kills efficiency of TCP/IP net data communication and DCOM
    net data communication is very inefficient. Here is the <a
    href="http://www.codeproject.com/useritems/SockFundamental.asp">recommended article</a>
    for you to read. Additionally, I also put two samples, <a
    href="http://www.codeproject.com/useritems/STutorial1.asp">socket development guide</a>
    and speed test to let you test it. MS highly recommends us three-tier development and
    pushing all (or as many as possible) of logical operations in the middle tier. After
    reading these articles, you will understand the essence of this recommedation more deeply.
    The essence of this recommendation is to avoid bad DCOM net data traffic between a client
    and a server over internet/intranet.<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; You maybe disagree with me, and say that my
    DCOM client-server application system works well to me. That is true only if a limited
    number of clients are connected to your DCOM server. That will be false if a large number
    of clients are involved. In this article, I will show you with a sample how to offset
    weaknesses of DCOM with socket for improving your DCOM server application performance a
    lot. <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </li>
  <li>Weaknesses of DCOM<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What are weaknesses of DCOM? Here is a list of
    weaknesses of DCOM.<ul>
      <li>Net efficiency is very low.</li>
      <li>DCOM calls are synchronous only, and can not be asynchronous. Connection points are
        faked asynchronous calls. This weakness complicates client side development in many cases.
        In order to solve lengthy calls problem, your DCOM clients will have to use threads to
        prevent client graphical user interfaces from being frozen. Threads will certainly hurt
        you if your application becomes large and complicate.</li>
      <li>You client applications never batch multiple calls into one. Lost of net data
        round-trips are involved.</li>
      <li>Many others like slow initialization server object and security setup etc.<br>
        &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </li>
    </ul>
  </li>
  <li>A perfect solution to DCOM with socket<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What advantages does socket have? If you read
    the above recommended articles, you will know the following advantages with socket.<ul>
      <li>Net efficieny is better. If lots of calls are involved, socket net efficiency is much
        better than DCOM.</li>
      <li>Socket supports both synchronous and asynchronous calls. This feature definitely
        simplify your client application development a lot. You will have much less chance to use
        worker threads to prevent client graphical user interfaces from being frozen.</li>
      <li>Your client applications could easily batch multiple calls into one with less code or
        without any code. Lost of net data round-trips are avoided.</li>
      <li>Your client applications can run multiple socket connections to a server. Each of the
        connections run independently and in parallel without creating any worker threads. You can
        use different socket sessions to process different calls at the same time.</li>
    </ul>
    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What disadvantages does socket have? Here is
    the list of socket disadvantages.<ul>
      <li>It is difficult to program server side applications because of multiple threads problem.
      </li>
      <li>You must handle socket security.</li>
    </ul>
    <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I already solve all of the above two socket
    problems for you. See the above articles. Attached with this exmple, you will find a
    socket-nized DCOM server with full C++ source code. Additionally you will see a VB client
    application with source code. It demonstrate the advantages of combination of socket and
    DCOM. It uses strong points of DCOM to offset socket weakness (security) in window
    platforms, and also uses strong points of socket to offset weaknesses of DCOM too. No
    hacker is able to directly hack this application socket communication unless the hacker
    hacks window DCOM system first. </p>
  </li>
  <li>Notes<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; No matter whether you like this article, I
    welcome to your comments. I am excited with this. Attention: I am also able to provide
    service to your company. Contact me at <a href="mailto:yekerui@yahoo.com">yekerui@yahoo.com</a>.</li>
</ol>
</body>
</html>

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here

Share

About the Author

Yuancai (Charlie) Ye
Web Developer
United States United States
Yuancai (Charlie) Ye, an experienced software engineer, lives in Atlanta, Georgia. He is an expert at OLEDB consumer and created a powerful data accessing libarary at the site http://www.udaparts.com. He has been working at SocketPro written from batching, asynchrony and parallel computation for more than three years. Visual C++, C# and ASP.NET are his favorite development environments.

| Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.150224.1 | Last Updated 24 Feb 2002
Article Copyright 2002 by Yuancai (Charlie) Ye
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid