Stuart McLachlan
stuart at lexacorp.com.pg
Sun Aug 30 18:30:02 CDT 2009
The only reason it "goes away" is because web services use the standard HTTP port 80 which is open by default on most routers. That means there is no configuration needed on the client machines. But you will still need "IT" to configure the router and set up port forwarding to point to the server hosting the web service. Of course, this is not an issue where you set up a web service on a public web server, but that is not what you are trying to do - you want something hosted internally which can access your internal file systems and databases and interface in a controlled manner with other machines. There's nothing to stop you from using the same port 80 for your own TCP/IP Listener application. You can also any of the other "standard" ports which are likely to be open on a router such as FTP (21), SMTP(25), POP3(110) etc I have a couple of such Listener applications which do the sort of things you are after, but they are written in PB/Win - if you want to look at them to get a better idea of oterh way you can do this, I will send the source to you off line. -- Stuart On 30 Aug 2009 at 18:18, jwcolby wrote: > Thanks Stuart. > > I believe one of the implications of the service route was that the whole TCP/IP address / port > thing goes away, IOW it can get through a firewall without having to get the intervention of IT. > > I am listening to all points of view. Luckily I am in no hurry here, it will be six months or more > before I need to solve this problem, or even have the requisite knowledge. > > John W. Colby > www.ColbyConsulting.com > > > Stuart McLachlan wrote: > > WCF, SOAP, Web Services etc are necessary if you are exposing services to all and > > sundry on the web. > > > > There are far simpler ways to exchange data when you have control of both the client and > > the server. These other methods do not require you to set up a web server and publish a > > schema which then opens up your data to the whole world. Take a look at a simple TCPIP > > client/server solution first. Here's a simple one in VB .Net > > > > http://www.eggheadcafe.com/articles/20020323.asp > > > > This could be easily modified to do the sort of thing you are after, with the Listener > > application doing most of the work. > > > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com >