Web和Windows应用程序之间的通信 [英] Communication between Web and Windows application
问题描述
我们正在开发一个电子商务应用程序，审核可以使用
用于订购药品。其中一个要求是Web应用程序
可以与使用MS-Access作为后端数据库的本地安装的实践管理应用程序进行通信。这种方式发货电子商务
订单我们可以在实践管理应用程序中导入更新
库存水平的药品。
Web应用程序将用ASP.NET / C＃编写。
我的问题：
我们应该使用哪种技术进行通信在浏览器中使用
实践管理应用程序的MS-Access后端？我在想使用C＃写一个ActiveX控件的
，并让Verisign签名。
这是一个很好的解决方案吗？有替代解决方案吗？接口
将由大约1500个客户使用。一个重要的方面是能够通过互联网部署代码。当前的订单应用程序是用VB编写的，需要从CD-ROM安装，这对于代码
更新来说是一场噩梦。这必须用ASP.NET应用程序替换，而
保持与本地安装的
实践管理应用程序同步数据的能力。
只需为客户端和Web应用程序使用相同的数据库。如果你有1500美元的b $ b用户，请注意Access不会允许多于10个（我认为它们是10个）并发用户，所以要小心与连接。如果你使用更强大的网络应用程序，那么你可以使用它为客户端应用程序
。
Jochen Neyens写道：
我们正在开发一个电子商务应用程序，兽医可以用它来订购药品。其中一个要求是Web应用程序可以与使用MS-Access作为后端数据库的本地安装的实践管理应用程序进行通信。这种方式发货的电子商务订单可以在实践管理应用程序中导入，以更新药品的库存水平。
Web应用程序将用ASP.NET编写/ C＃。
我的问题：
我们应该使用哪种技术在浏览器中与实践管理应用程序的MS-Access后端进行通信？我正在考虑使用C＃编写ActiveX控件，并让Verisign签名。这将是一个很好的解决方案吗？有替代解决方案吗？大约1500个客户将使用该界面
。一个重要的方面是通过Internet部署代码的能力。当前的订单应用程序是用VB编写的，需要从CD-Rom安装，这是代码更新的噩梦。这必须用ASP.NET应用程序替换，同时保持与本地安装的实践管理应用程序同步数据的能力。
" Jochen Neyens" < JN ***** @ analyz-it.be>在消息中写道
新闻：eX ************** @ TK2MSFTNGP09.phx.gbl ...
我们我正在开发一个电子商务应用程序，该应用程序可以用来订购药品。其中一个要求是web
应用程序可以与使用MS-Access作为后端数据库的本地安装的实践管理应用程序进行通信。这种方式发货电子商务我们可以在实践管理应用程序中导入订单来更新药品的库存水平。
Web应用程序将用ASP.NET编写/ C＃。
我的问题：
我们应该使用哪种技术在浏览器中与实践管理应用程序的MS-Access后端进行通信？考虑使用C＃编写ActiveX控件，我想是
，让Verisign签名。这将是一个很好的解决方案吗？有替代解决方案吗？大约1500个客户将使用该界面
。一个重要的方面是通过Internet部署代码的能力。当前的订单应用程序是用
VB 5编写的，需要从CD-Rom安装，这是代码更新的噩梦。这必须用ASP.NET应用程序替换，同时保持与本地安装的实践管理应用程序同步数据的能力。
" Jochen Neyens" < JN ***** @ analyz-it.be>写在消息
新闻：eX ************** @ TK2MSFTNGP09.phx.gbl ...
首先，MS-Access，即使是最新版本也是完全错误的
解决方案！正如已经提到的那样，这种方式限制为10个/ b $ b并发网络用户。当第11个并发用户尝试访问该网站时，他们将坐下来等待与Access数据库的连接
变为可用。真。算了吧！
其次，是否有必要部署本地代码？为什么不只是
去寻找基于浏览器的解决方案？这样，你所有1500个用户需要的是一个
连接到互联网（他们在你的场景下他们需要的是为了进行数据同步而需要的b $ b）和一个网络浏览器。
我几乎可以保证你在部署中节省的资金和
维护将远远超过你在SQL Server中的初始支出。 />
We''re in the process of developing an e-commerce application that vets can
use to order medicines. One of the requirements is that the web application
can communicate with a locally installed practice management application
that uses MS-Access as a backend database. This way shipped e-commerce
orders can we imported in the practice management application to update the
stock levels of medicines.
The web-application will be written in ASP.NET / C#.
My question:
Which technology should we use to communicate from within the browser with
the MS-Access backend of the practice management application? I was thinking
of writing an ActiveX control using C# and let this sign by Verisign. Will
this be a good solution? Is there an alternative solution? The interface
will be used by approx 1500 clients. An important aspect is the ability to
deploy code via the Internet. The current order application is written in VB
5 and needs to be installed from a CD-Rom which is a nightmare for code
updates. This has to be replaced with an ASP.NET application whilst
maintaining the ability the synchronise data with the locally installed
practice management application.
Just use the same database for the client and web applications. If you have
1500 users though, be warned that Access won''t allow more then 10 (I think
it''s 10) concurrent users, so be careful with the connections. If you are
using something more robust for the web app, then use that for the client app
as well.
"Jochen Neyens" wrote:
We''re in the process of developing an e-commerce application that vets can
use to order medicines. One of the requirements is that the web application
can communicate with a locally installed practice management application
that uses MS-Access as a backend database. This way shipped e-commerce
orders can we imported in the practice management application to update the
stock levels of medicines.
The web-application will be written in ASP.NET / C#.
My question:
Which technology should we use to communicate from within the browser with
the MS-Access backend of the practice management application? I was thinking
of writing an ActiveX control using C# and let this sign by Verisign. Will
this be a good solution? Is there an alternative solution? The interface
will be used by approx 1500 clients. An important aspect is the ability to
deploy code via the Internet. The current order application is written in VB
5 and needs to be installed from a CD-Rom which is a nightmare for code
updates. This has to be replaced with an ASP.NET application whilst
maintaining the ability the synchronise data with the locally installed
practice management application.
"Jochen Neyens" <jn*****@analyz-it.be> wrote in message
news:eX**************@TK2MSFTNGP09.phx.gbl...
We''re in the process of developing an e-commerce application that vets can
use to order medicines. One of the requirements is that the web application can communicate with a locally installed practice management application
that uses MS-Access as a backend database. This way shipped e-commerce
orders can we imported in the practice management application to update the stock levels of medicines.
The web-application will be written in ASP.NET / C#.
My question:
Which technology should we use to communicate from within the browser with
the MS-Access backend of the practice management application? I was thinking of writing an ActiveX control using C# and let this sign by Verisign. Will
this be a good solution? Is there an alternative solution? The interface
will be used by approx 1500 clients. An important aspect is the ability to
deploy code via the Internet. The current order application is written in VB 5 and needs to be installed from a CD-Rom which is a nightmare for code
updates. This has to be replaced with an ASP.NET application whilst
maintaining the ability the synchronise data with the locally installed
practice management application.
"Jochen Neyens" <jn*****@analyz-it.be> wrote in message
news:eX**************@TK2MSFTNGP09.phx.gbl...
Firstly, MS-Access, even the very latest version is totally the wrong
solution for this! As has already been mentioned, you''re limited to 10
concurrent web users this way. When the 11th concurrent user tries to access
the site, they will sit and wait until a connection to the Access database
becomes available. Really. Forget it!
Secondly, is there any necessity to deploy local code at all? Why not just
go for a browser-based solution? That way, all your 1500 users require is a
connection to the Internet (which they would need anyway under your scenario
in order to do the data synchronisation) and a web browser.
I can virtually guarantee that the money you''ll save in deployment and
maintenance will far outweigh your initial outlay in SQL Server.
这篇关于Web和Windows应用程序之间的通信的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
