1

I am working out the nitty gritty of a potential server / many-client project and it's in a realm I haven't been before. Disregarding the scale of the project for a moment and assuming this ever goes ahead....

My current idea is that the server should be a fat server with a thin rich client on each workstation, built in C# .NET and probably using WinForms for the user interface, and distributed via ClickOnce for easy and compliant software updating.

Database <-> Server (business logic) <-> Rich Thin Client

Instead of a fat client:

Database <-> Client

I am looking into WCF for the server. Is this advisable for a client-server architecture with the following usage case?

  • Anywhere between 10 and 100 receptionists and practitioners using the client (company growth would increase this)
  • Windows 7 and up being primary workstation operating system
  • Minimal data traffic desirable
  • Potential for large data to be stored alongside the database in some manner (patient images, video and such)

Is it wise for the server to be performing business logic as much as possible and only sending information and results and doing the basics on the client (validation etc)? It seems logical to me.

Does anyone have some good information on beginning such a big project?

I believe the current software being used is actually a fat client with a direct MSSQL connection.

Not only this, it is also non-distributed and each clinic has it's own separate database causing many problems with data integrity and collation for reporting and such.

4

1 回答 1

0

这对您的架构来说是完全有效的计划。WCF 会做得很好。如果您需要有关验证用户身份的 Web 应用程序和从应用程序内运行的 ClickOnce 模块之间身份验证共享的教程，我曾经写过一篇：

http://www.wiktorzychla.com/2008/02/clickonce-webservice-and-shared-forms.html

这是几年前写的，虽然我展示了如何在 ClickOnce 和 ASMX Web 服务之间共享身份验证，但后来我写了另一个关于在 Silverlight 模块和 WCF 服务之间共享身份验证的教程。

http://www.wiktorzychla.com/2010/04/aspnet-forms-authentication-sharing-for.html

将这两者结合起来将为您提供 ClickOnce + WCF 身份验证共享。

于 2013-11-14T07:23:26.870 回答