DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: Web Services

  1. #1
    Michael Welch Guest

    Re: Web Services

    Michael,
    >
    > What does everyone think?
    >


    We were just discussing this at work. Someone mentioned a cartoon they saw
    recently. The caption said something like: "Look at this, we implemented
    TCP/IP over SOAP" That eliminates the firewall problem. ;-)

    Michael





  2. #2
    Michael Culley Guest

    Web Services

    I've been looking at webservices and have seen books + docs say that the
    great thing about web services is that they use http, hence port 80 and so
    dont't have any problems with firewalls, as port 80 is usually left open. I
    have seen this sort of thing mentioned before. What I'm thinking is "doesn't
    this defeat the purpose of having a firewall?". I mean, why don't we put
    everything on port 80, wouldn't this solve the firewall "problem" once and
    for all?

    What does everyone think?

    --
    Michael Culley
    www.vbdotcom.com





  3. #3
    Zane Thomas [.NET MVP] Guest

    Re: Web Services

    On Fri, 15 Mar 2002 21:45:12 -0600, "Michael Welch"
    <billshewman@hotmail.com> wrote:

    >That eliminates the firewall problem.


    Yep, 2400baud tcp/ip just like the good <cough> old days.


    --
    Turn on, tune in, download.
    zane@mabry.com

  4. #4
    Ed Guest

    Re: Web Services


    "Michael Culley" <m_culley@hotmail.com> wrote:
    >I've been looking at webservices and have seen books + docs say that the
    >great thing about web services is that they use http, hence port 80 and

    so
    >dont't have any problems with firewalls, as port 80 is usually left open.

    I
    >have seen this sort of thing mentioned before. What I'm thinking is "doesn't
    >this defeat the purpose of having a firewall?". I mean, why don't we put
    >everything on port 80, wouldn't this solve the firewall "problem" once and
    >for all?
    >
    >

    The issue is that other protocols such as DCOM want to use a wide range of
    ports but the security police have a problem with opening too many ports
    to the Internet. In fact, most of them would like to shut down all the ports
    but fortunately, cooler heads pervail and they allow port 80. Therefore,
    the advantage of using SOAP is that you can use remote procedure calls using
    port 80 and not worry about the security police telling you can't use SOAP
    because it uses too many ports or the wrong ports. This doesn't make it
    more secure as such other than you may have something monitoring what is
    going through Port 80 and hopefully stopping anything that looks suspicious.
    I would expect that if Web Services takes off then someone will develop
    a firewall that will ensure only traffic that adheres to specific SOAP calls
    will be allowed. You may even have something that ensures that only valid
    data is supplied in the call's parameters as defined by an XML Schema or
    such. This will help in preventing someone sending binary data that could
    be executed on your server.









Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center