1

I have a web application which process the data collected from different client machines (1000-1500 client machines) and shows the results in graphical format.

The client machine generates an Excel sheet periodically and this excel sheet needs to be transfered to the server after every 30 minutes.

I want your help to identify the right approach to write this client component (Windows) which will generate and upload the excel sheet automatically after a specified time duration. I would also like help identifying the right approach for the server component which will recieve and save the data uploaded by clients.

Should we use an FTP-like implementation for the server side component?

Improve this question
1
  • What happens to the old spreadsheet from the client after 30 minutes? Is it overwritten, or is this a cumulative thing where all the old ones are kept on the server? If it's a cumulative thing, is this a problem area, or do you have something worked out for looking at older versions? Commented Jun 18, 2012 at 5:04

1 Answer 1

Reset to default
1

Since you already have a web application then using the HTTP protocol would be easier because you can (presumably) easily create a new request handler to accept the file.

Create a new route which accepts POST requests to a URI and takes the request body as the Excel spreadsheet. The handler for this route will handle the storage and processing of the file. The client needs only to know the correct route and to properly submit the HTTP request.

FTP is a somewhat antiquated protocol due to better security and library support for newer ones such as SCP/SFTP and HTTP.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.