Hi,
This is a followup of the following thread .
I decided to expose my requirements and eventually get feedback from the community. I have spent the WE looking for various options and I have found so many that I would really need advice on which technologies to use.
Introduction:
I want to be able to delegate to other computers calculation work. This is currently running locally, but takes all the ressources of the workstation. So submitting a job to one ore more specially dedicated stations seems like a reasonable approach.
OS:
Mainly Windows XP, eventually 2000 and Vista one day.
General idea:
The user submits a job to one of the available workstations and then has an option to view what is happening on this machine. It's a quite simple form, with a listview containning several columns that need to be syncronized with the same form on the batch station (client <=> server). From this form, the user should be able to send simple requests such as "put on hold", "cancel", ... This should work in a LAN/WAN environment. I could be wrong, but this does look a lot like printing through a printserver.
Technologies:
This is the various techologies I have found:
[ul]
[li]Socket connections[/li]
[li]Microsoft Message Queuing[/li]
[li]Web Services[/li]
[li]TCP Remoting[/li]
[/ul]
Points that need attention:
[ul]
[li]To send information from client to server and back, I wanted to use xml to have something rather open for futur modifications. Any comments?[/li]
[li]In order to update a listview from server, I was thinking of serialization: is this reasonable, efficient or overdone?[/li]
[li]Is it worthwile using encryption and/or compression?[/li]
[li]If max +/-30 clients connect to a server application, are multi-treads required?[/li]
[/ul]
I generally do a lot of searching myself, but in this case I just cannot study all of these technologies, experiment them and finally decide.
An advice, ideas or suggestions are really welcome.
AD AUGUSTA PER ANGUSTA
Thierry
This is a followup of the following thread .
I decided to expose my requirements and eventually get feedback from the community. I have spent the WE looking for various options and I have found so many that I would really need advice on which technologies to use.
Introduction:
I want to be able to delegate to other computers calculation work. This is currently running locally, but takes all the ressources of the workstation. So submitting a job to one ore more specially dedicated stations seems like a reasonable approach.
OS:
Mainly Windows XP, eventually 2000 and Vista one day.
General idea:
The user submits a job to one of the available workstations and then has an option to view what is happening on this machine. It's a quite simple form, with a listview containning several columns that need to be syncronized with the same form on the batch station (client <=> server). From this form, the user should be able to send simple requests such as "put on hold", "cancel", ... This should work in a LAN/WAN environment. I could be wrong, but this does look a lot like printing through a printserver.
Technologies:
This is the various techologies I have found:
[ul]
[li]Socket connections[/li]
[li]Microsoft Message Queuing[/li]
[li]Web Services[/li]
[li]TCP Remoting[/li]
[/ul]
Points that need attention:
[ul]
[li]To send information from client to server and back, I wanted to use xml to have something rather open for futur modifications. Any comments?[/li]
[li]In order to update a listview from server, I was thinking of serialization: is this reasonable, efficient or overdone?[/li]
[li]Is it worthwile using encryption and/or compression?[/li]
[li]If max +/-30 clients connect to a server application, are multi-treads required?[/li]
[/ul]
I generally do a lot of searching myself, but in this case I just cannot study all of these technologies, experiment them and finally decide.
An advice, ideas or suggestions are really welcome.
AD AUGUSTA PER ANGUSTA
Thierry
