Home > Archive > C# > December 2005 > Need Your Opinion
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| StratCat 2005-12-13, 8:35 am |
| Hello,
My name is Robert and I am doing some software testing of a C# program for one of the national banks. I am to present my findings on this product to my managers, as I will also be one of the users, and basically it does not need to be implemented due to what I feel is poor program design. I would like to offer a description of how the product operates and get your opinion as C# programmers if this design is based on a sound theory, or if its simply the wrong way.
The program interfaces with an Exchange server and whenever an email is received it has a trigger that pulls a copy into the database. This is so that the agents in the department can track the email, create a ticket, resolve, and close. Here are the facts as I know it.
Created in C#
Uses SQL backend.
Infragistics Interface.
Now instead of being what I consider a true Client/Server application this progam operates in what I consider to be an unconventional method.
The program has the copy of the DB on the server(21,000 emails) and when a client connects it downloads the entire DB into the virtual memory of the machine. So each client connecting pulls 21,000 email headers into their VM for as long as they are using the product. ( Read 10mins- 1hour load time depending on proc speed) (Generally 100% proc usage)
Now, when changes are made it is supposed record these changes to the connected clients immediately, but so far does not seem to be doing so.
I just need to hear from you guys/girls if this is sound design or if this is poor coding. I sincerely appreciate your time, and if I need to offer any further information please do not hesitate to ask.
Robert Rowe. | |
| spalding 2005-12-19, 8:42 pm |
| Hi
Where do the clients view these email headers? Web form, desktop app, some other client?
Returning 21,000 records to the end user every time they query the system is, in my opinion, probably not the ideal solution, especially if you envisage the number of records and or clients growing considerably in the near future. You have to remember that this puts a strain not just on each client but on the SQL Server as well.
Is it possible to cache the headers to permanent storage on the client's computer and update the list every time they connect? Obviously there are other solutions, each depending on how the user views the emails.
Hope this answers your question. |
|
|
|
|