G
Guest
May be the this is not the right group to post this.
But this is the only group which helps me to receive instant and valuable replies.
This is the reason I am posting this here. Excuse me for this.
We have decided a design, I would suggest if some onw help me to evaluate.
We have a windows application which is using webservices.
The client has to export certain files which requires the documents to be generated
first and then put them in xml envelope and send it to respective webservice.
The client should not wait till the document generated. But the system will have provision to show the export successfull or not?
Design -
Client sends a request to the webservice. Webservice puts the request into MSMQ.
Webservice sends the response to client that the request is received.
Now a Windows service is designed on the Server which reads the queue and based on the message fetches the data from database and generates the document.The documents are generated and saved in the database and a message is saved in the MSMQ that the documents are generated for the request of client.
Now Another windows service reads the MSMQ for the the request whose documetns are complete. That service gets the documents from database and sends the documents to another webservice. After successfull upload the windows service updates the database that the export is sucessfull.
Questions-
1. Can we have a alternative to the MSMQ?
2. We want to minimize the hits to the database. hence queing in database will be performance hit as we will have to poll the database or queue in every second(we are expecting lot of request to export) .
3. Having a queue in mdb file or in xml file would be a problem as these have their own limitations?
4. If the document generated happens to be on the client side, it would result lot of hits to webservices to get the data from the database. The data to generate the document can not be fetched in one hit.
Thanks in advance.
dinoo
But this is the only group which helps me to receive instant and valuable replies.
This is the reason I am posting this here. Excuse me for this.
We have decided a design, I would suggest if some onw help me to evaluate.
We have a windows application which is using webservices.
The client has to export certain files which requires the documents to be generated
first and then put them in xml envelope and send it to respective webservice.
The client should not wait till the document generated. But the system will have provision to show the export successfull or not?
Design -
Client sends a request to the webservice. Webservice puts the request into MSMQ.
Webservice sends the response to client that the request is received.
Now a Windows service is designed on the Server which reads the queue and based on the message fetches the data from database and generates the document.The documents are generated and saved in the database and a message is saved in the MSMQ that the documents are generated for the request of client.
Now Another windows service reads the MSMQ for the the request whose documetns are complete. That service gets the documents from database and sends the documents to another webservice. After successfull upload the windows service updates the database that the export is sucessfull.
Questions-
1. Can we have a alternative to the MSMQ?
2. We want to minimize the hits to the database. hence queing in database will be performance hit as we will have to poll the database or queue in every second(we are expecting lot of request to export) .
3. Having a queue in mdb file or in xml file would be a problem as these have their own limitations?
4. If the document generated happens to be on the client side, it would result lot of hits to webservices to get the data from the database. The data to generate the document can not be fetched in one hit.
Thanks in advance.
dinoo