I am thinking that this is the right forum to post my message. If you don't think so I would appreciate if you can move this to the right forum.
Here goes how architecture of the base application works. When user logs into the system and requests server to create a new Quote, request is sent to server to get the huge XML file with all the nodes that would hold Quote data entered by the user. This is done through event handlers that update this XML documnet when user enters some data.On save this XML document is submitted to the server, which would save it to the database.
Current project is like adding new functionality to the base project for a differnt type of quote and user should be able to switch between the quotes, which makes me think that this new quote type is part of the current application and code for new Quote should be within the current aplication. I was thinking of Update exisitng XML document to hold new properties of the new Quote.
Disadvantage I see with this approach is: If say down the line, if some other quote type comes up or if business rules for exisitng quote type changes (addition/delete), then it would be a night mare to mantian this huge XML document.
If I try to maintain seperate XML documents for each quote type and as this XML document is generated by the server, which is reterived on load of the application, whenever user updates the quote type, I will have to make a server trip to save exisiting quote and retrieve XML quote (inorder to persist the information entered by the user) for the selected quote type, which would effect performance of the application.
I want to design this application to be modular enough and less maintainable.
Can you please suggest right approach for such a problem. early reply would be greatly appreciated.
Thank you [ March 01, 2006: Message edited by: s penumudi ]
CAUTION! Do not touch the blades on your neck propeller while they are active. Tiny ad: