从 ASP.NET MVC 应用程序发送传真
我正在开发 ASP.NET MVC 应用程序，作为我大学暑期实习工作的一部分。 我有一个要求，我需要实现传真功能。 因为我还是学生，这是我的第一个真正的应用程序，所以我有点困惑如何制作这个函数以及我应该使用哪些库。由于应用程序的性质，不考虑第三方服务（例如邮件到传真等）——它将是帮助医生接触患者的服务。该数据是私有的，不能发送给任何第三方服务。
如果这很重要的话，我正在使用 Visual Web Developer 2008 Express 版本。
传真机将安装在服务器上，传真将从那里发送。 我正在寻找建议，或者也许是一些可以帮助我的好资源。 谢谢。
I am developing ASP.NET MVC application as a part of summer experience job from my college.
I have a requirement where i need to implement a fax functionality.
Because i am still student, and this is my first real application, i'm kinda confused how to make this function and what libraries should i use. Third party services (such as mail to fax and so on) are not considered due to the nature of application - it is going to be a service that help doctors to get access to patients encounters. This data is private and cannot be sent to any third party service.
I am using Visual Web Developer 2008 express edition if this matters.
The fax machine is going to be installed on the server, and faxes will be sent from there.
I am looking for advice or, maybe some good resources that can help me.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我在我们的应用程序中从事传真工作。我们的应用程序通过配置选项与各种传真服务集成。我建议购买或使用现成的东西并与之集成。一些示例包括：
Microsoft 传真服务器，免费
现有 Windows Server 许可证。
Faxman，只需象征性的费用
收费，效果很好。可以通过以下方式传真 PDF：
可选的附加组件。
RightFax 非常昂贵
解决方案。可以使用传真传真 PDF
可选插件。
您可以查看适配器模式来从您的服务中抽象传真实现。
I've worked on faxing in our application. Our app integrates with various fax services through configuration options. I recommend buying or using something off-the-shelf and integrating with it. Some examples include:
Microsoft Fax Server, free with
existing Windows Server licenses.
Faxman, which costs a nominal
fee, works great. Can fax PDFs with
an optional add-on.
RightFax is a very expensive
solution. Can fax PDFs with an
optional add-on.
You might look into the Adapter pattern to abstract the faxing implementation from your service.
这里最简单的方法是使用某种电子邮件到传真设施（本地托管或云端托管）来发送传真。将使您的生活变得更加轻松，因为您不必再回到老学校并沉迷于拨号音。
如果您确实必须发送内容，您可能应该考虑将操作外部化到您自己的服务，原因如下：
1）可测试性/可维护性/流程——如果它是外部的，您可以创建一个存根 API 并编写您的 Web 应用程序来进行对话首先，然后再处理拨号音。但这不是一个阻塞问题。而且您的测试套件不需要传真调制解调器。
2) 可用性——传真如果成功发送，则需要一段时间才能发送。快速传递请求并告诉用户请求已发送，然后通知他们成功，这比长时间运行的“处理”图形更有意义。
The easiest approach here would be to use some sort of email to fax facility--either hosted locally or in the cloud--to send the faxes. Will make your life much, much easier as you won't have to take it back to the old school and get down with dialtones.
If you do have to send stuff, you should probably look at externalizing the operation to your own service for a few reasons:
1) testability/maintainability/flow -- if its external you can create a stubbed API and write your web app to talk to that first, then get down with dialtones later. But its not a blocking issue. And your test suite doesn't need a faxmodem.
2) usability -- faxes take a while to send, if they succeed at all. Passing off the request quickly and telling a user its being sent then notifying them of success makes a bit more sense then a really long running "PROCESSING" graphic.
我首先查看 TAPI，它是 Microsoft 的电话 API。维基百科页面中列出了 .Net 包装器。
I'd start by looking at TAPI, which is Microsoft's Telephony API. There are .Net wrappers listed in the Wikipedia page.