given that your using RAS (wow, thats a term I havne't heard in awhile. =))
your probably within the computer running the application. in which case, i
doesn't really matter that much. Webservices, useful for the extranet
because it uses port 80 and helps with firewall issues.. Also, everything
comes back in SOAP.
Sockets, are you bored? Then yeah, go with that...
Remoting. Kinda like a web service, very much like a web service but you
define the TCP socket.
So basically, it comes to the fact of how much work you want to do. With
Remoting, you have to set up a remoting server, sockets same thing.
WebService already implemented through IIS.
It's preference at this point, your security isn't a huge issue since your
using RAS, so my opinion, do whats comfortable.
-CJ
"Ken Hughes" <an*******@discussions.microsoft.com> wrote in message
news:F6**********************************@microsof t.com...
Hi,
I'm looking for some advice on architecure - apologies if this is the
incorrect group...
I'm writing a VB app and it has to pass data to a another server machine
(in a different office). There is no permanent connection between the two
machines also the server machine does not have a 'public' server. So I'm
planning on having the remote machine use RAS to connect to the server.
The Question:
I have to pass some data (XML ??) from the remote to the server is my best
option to :-
1. Use Remoting
2. Implement a WebService on the server and use that
3. Implement my own Sockets connection
Any pointers or thoughts / comments appreciated..
.. ken
