Windows 上的 POS 开发：通过 COM 的 OPOS？适用于 .Net 的 OPOS？统一POS？ ...？
我计划从头开始开发一个POS系统，该系统将基于windows（目前是XP SP3）。我尝试了解使用哪个 API 来处理 POS 设备。到目前为止，我发现 OPOS 是作为一组 COM 对象实现的、一个似乎基于 COM 对象的 .Net 库以及一个名为 UnifiedPOS 的即将推出的标准。
问题是，COM 对象似乎很旧，并且 .Net 内容自 .Net 1.1 以来就没有更新。但我无法找到 UnifiedPOS 规范的实现。
有人知道 Windows 版 UnifiedPOS SDK 之类的东西吗？或者有人可以推荐使用 OPOS 或任何其他 API？
I plan to develop a POS system from scratch, which will be based on windows (currently XP SP3). I tried to get an overview of which API to use to work with POS devices. So far I found OPOS which is implemented as a set of COM objects, a .Net library which seems to be based on the COM objects and an upcomming standard called UnifiedPOS.
The problem is, that the COM objects seem to be quite old and the .Net stuff has not been updated since .Net 1.1. But I was not able to find an implementation of the UnifiedPOS specification.
Does somebody know something like a UnifiedPOS SDK for windows? Or could somebody recommend the usage of OPOS or any other API?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
OPOS 真正以成员公司董事会商定的标准启动了所有 POS API，以帮助提高 POS 特定计算机硬件的互换性。 OPOS 信息 如果您购买了 POS 软件，则不会出现此信息由于软件的编码方式，必然会遇到供应商锁定。
JavaPOS 规范只是将过时的基于 OLE 的 API 转换为 Java，这可能是某些人首选的开发环境。 JavaPOS Info
当然不是每个人都喜欢 Java，请进入 POS.net，它是 Java 的另一个孩子OPOS 但由 Microsoft 基于 .NET 框架构建。POS.net 信息 POS.net 向后兼容 OPOS 驱动程序。因此，任何支持 OPOS 的设备也可以支持 POS.net。 （许多硬件供应商甚至在只提供 OPOS 驱动程序时声称具有 POS.net 兼容性。）
所有这些库的目的是标准化对不同供应商的硬件设备的访问。 您对库的选择主要取决于您对开发环境的选择。值得注意的是，一些主要硬件供应商在形成这些库的标准组织中的影响力使得它们并不是真正100%与供应商无关。因此，许多 POS 开发人员构建了自己的硬件抽象层，然后可以依次调用 POS.net 或通过 RS232 或 TCP/IP 直接与其 POS 硬件通信。
此外，POS 行业在技术上普遍落后，并且受到低成本和普遍缺乏对最新强大硬件的需求的推动。 POS.net SDK 不需要 .NET 3.5/4.0 的任何功能，因此不会针对它重新编译。相反，POS 供应商通常希望在低功率商用硬件上运行他们的软件。这些系统通常运行 Windows XP 或 Windows XP Embedded（XP 没有消费者的东西），因为与 Vista 相比，其在存储和 RAM 中的内存占用更低，并且总体速度更快（Win7 可能会改变这一点，但正如我提到的，POS 行业存在滞后）与其他行业相比，软件采用率更高）。
OPOS really started all the POS APIs with a standard agreed on by a board of member companies to help make POS specific computer hardware more interchangeable. OPOS Info This was if you purchased a POS software you wouldn't necessarily experience vendor lock due to the way the software was coded.
JavaPOS specification simply turned the outdated OLE based API into Java which may be some people's preferred development environment. JavaPOS Info
Of course not everyone loves Java, Enter POS.net, another child of OPOS but built on .NET framework by Microsoft.POS.net Info POS.net is backwards compatible with OPOS drivers. So any device that works with OPOS also works with POS.net. (Many hardware vendors even claim POS.net compatibility when they only supply OPOS drivers.)
The point of ALL of these libraries is to standardize access to hardware devices from different vendors. Your choice of library will be mostly dependent on your choice of development environment. It is worth noting that the influence of some major hardware vendors in the standards organizations that formed these libraries makes them not really 100% vendor agnostic. For that reason many POS developers build their own hardware abstraction layer, that can then in turn call on POS.net or talk directly via RS232 or TCP/IP to their POS hardware.
Also the POS industry in general lags behind in technology and is driven by low cost and the general lack of a need for the latest powerful hardware. The POS.net SDK doesn't need any of the features of a .NET 3.5/4.0 and hence won't be recompiled against it. Instead POS vendors often want to run their software on low powered commodity hardware. These systems often run Windows XP or Windows XP Embedded (XP without the consumer stuff) for its lower memory footprint both on storage and in RAM and general speediness compared to Vista (Win7 may change that, but as I mentioned the POS industry has a lag in software adoption compared to other industries).