S
scorpion53061
Hi,
I am looking for a code sample that communicates from a client to a
remote Windows Service on another computer over the internet, that is
the Windows Service performing instructions the client sends. That being
said, I also would like feedback on this.
Currently in my Windows applications, I do a lot of communication with
my servers at work from customers to place orders, check stock status
etc. The production server is a AIX system and I do screen scraping. The
commands are coming from the client and going straight to this server.
In addition, the client does the office automation and the actual
communication of the commands to this server.
I am thinking in the next release to do this.
Have a Windows Service located on the Windows 2003 Server that all the
client does is communicates its intentions to the Service. The service
will actually do the communicating of the commands to the AIX Server (it
is high overhead on the client). Also, I was thinking that the reporting
that is being done could be done by the Windows Service (office
automation) and then the documents sent to the client via email or FTP.
Then I am freed from Worries about them not having the right office
version and those considerations. I could even actually use the XML
features within Office 2003 which I have not been able to do up to this
point since most of my business customers have refused to upgrade (when
I dropped Office 97 support you would have thought I was the devil.) The
role of the client would primarily be to maintain the communication with
the server but all the work would be done there for each user running
the program.
What do you all think of these concepts?
I am looking for a code sample that communicates from a client to a
remote Windows Service on another computer over the internet, that is
the Windows Service performing instructions the client sends. That being
said, I also would like feedback on this.
Currently in my Windows applications, I do a lot of communication with
my servers at work from customers to place orders, check stock status
etc. The production server is a AIX system and I do screen scraping. The
commands are coming from the client and going straight to this server.
In addition, the client does the office automation and the actual
communication of the commands to this server.
I am thinking in the next release to do this.
Have a Windows Service located on the Windows 2003 Server that all the
client does is communicates its intentions to the Service. The service
will actually do the communicating of the commands to the AIX Server (it
is high overhead on the client). Also, I was thinking that the reporting
that is being done could be done by the Windows Service (office
automation) and then the documents sent to the client via email or FTP.
Then I am freed from Worries about them not having the right office
version and those considerations. I could even actually use the XML
features within Office 2003 which I have not been able to do up to this
point since most of my business customers have refused to upgrade (when
I dropped Office 97 support you would have thought I was the devil.) The
role of the client would primarily be to maintain the communication with
the server but all the work would be done there for each user running
the program.
What do you all think of these concepts?