Hi,
I am trying to decide the best middle tier method for the system I am
currently building. There are no issues of supporting previous
software versions, etc as this is a completely new company. The
company in question currently has 10 client pcs (which is likely to
grow rapidly), each of which will need to get some data from a
database, display it on screen for editing and of course write it
back. The data has to be distributed in such a way that a client must
get the next record in turn, with no 2 clients getting the same
record. I would like to write this using ASP.net ideally, unless
someone convinces me winforms is the better option. There are a few
solutions as I see it for the middle tier;
*Use a web service to serve and update the database. Using
transactions in SQL Server to stop duplicate records. - This would be
easiest for me to implement
*Create a COM+ component to serve as the middle tier, using MTS to
manage the transactions. - I don't know much about this route to be
able to know whether it would work.
I am a VB6 developer who has been studying C# for a couple of months,
I don't know enough about .net to be able to weigh up pros and cons.
Are there any other routes I should consider?
I'd be grateful for any comments
Jason
