TIBCO.EMS .NET 客户端/WCF 通道
各位，
TIBCO 早在 4 月份就宣布支持 WCF 通道 - 现在有什么实现了吗？
我在哪里以及如何下载这些新的 WCF 通道位，或者在哪里可以获得“TIBCO.EMS .NET 客户端库”的当前 .NET 2.0/3.5 版本？
到目前为止，我们是一家与 TIBCO 没有任何联系的小型 ISV，但我们的一个大客户要求我们与他的 TIBCO EMS 系统进行互操作，但无法提供我们需要的技术背景信息:-(
感谢您的任何提示和指示！ Marc
跟进 - 2009 年 1 月 14 日：这里没有太多回应......你们这些使用 TIBCO EMS 的人 - 如何与其交互，例如来回通信和发送数据？
更新（2010 年 4 月）
我有机会查看.NET 中的“本机”TIBCO.EMS.dll 及其 WCF 实现，我的结论是：使用本机 API。 这很容易，很简单，很有效。
WCF 部分太可怕了。 他们不完整，非常不传统，他们感觉自己不是一个好的 WCF 公民。 TIBCO 仅提供传输元素 - 您不能只使用现成的 emsBinding 或其他东西 - 您必须自己定义它。 我非常失望 - 我对 TIBCO 这样规模和声誉的公司抱有更高的期望......
Folks,
TIBCO has announced support for WCF channels back in April - has anything of that materialized by now??
Where and how can I download either these new WCF channel bits, or where can I get my hands on a current .NET 2.0/3.5 version of the "TIBCO.EMS .NET client library" ??
We're a small ISV without any ties to TIBCO so far, but a large client of ours required us to interop with his TIBCO EMS system, without being able to provide the technical background info we need :-(
Thanks for any hints and pointers !
Marc
Follow-up - 2009-Jan-14: Not much response here.... those of you using TIBCO EMS - how do you interface with it, e.g. communicate and send data back and forth??
UPDATE (April 2010)
I've had an opportunity to check out the "native" TIBCO.EMS.dll from .NET, as well as their WCF implementation, and my conclusion is: use the native API. It's easy, it's simple, it works.
The WCF parts are horrendous. They're incomplete, very unconventional, they don't feel like a good WCF citizen. TIBCO only provides a transport element - you can't just use a ready-made emsBinding or something - you'll have to define that yourself. I was very disappointed - I had expected more from a company the size and reputation of TIBCO....
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果您直接使用 Tibco EMS .NET 客户端，您的通信堆栈将会简单得多。 它的风格仿照 JMS，广泛应用于企业软件开发。 因此，有很多关于如何进行 JMS 编程的技术书籍。 Java 和 C# 非常相似，因此很容易将其应用于 Tibco EMS .NET 客户端编程。
在为分布式应用程序设计和实现了许多通信通道之后，我的经验是堆栈越简单，操作就越可靠且无故障。
WCF 之流的抽象层的问题在于，几乎总是潜伏在某处的抽象漏洞问题。
Your communication stack will be a lot simpler if you simply use Tibco EMS .NET client directly. It's styled after JMS, which is widely used in enterprise software development. Hence there are a lot of tech books on how to do JMS programming. Java and C# are so similar that it's easy to do the mental translation to apply that to Tibco EMS .NET client programming.
Having designed and implemented a lot of communications channels for distributed applications, my experience has been the simpler the stack the more reliable and trouble-free in operation.
The problem with abstraction layers of the ilk of WCF is that there is almost always a leaky abstraction issue lurking somewhere.
对于 tibco 和 wcf，您需要运行至少 4.4.3 版本作为 tibco 支持的最低版本。 否则你将不得不使用那里的标准协议。 他们确实有 .net，所以你不必进行互操作。 我还没有使用过 WCF 组件，因为我工作的地方仍然是 4.3.0，虽然他们说它应该可以工作，但它不受支持。 我们刚刚得到了这些位，因为我们应该很快更新到 5。
要获得这些部分，如果客户希望您使用它，您必须从客户那里获取它们。 这是我的观点，但您最好的选择是联系 Tibco，看看是否可以解决问题。
但最大的问题是您的客户使用的是哪个版本的 Tibco EMS。
For tibco and wcf you need to be running at least version 4.4.3 as the minimum that tibco supports. Otherwise you will have to use there standard protocol. They do have .net so you should not have to do interop. I have not used the WCF component as of yet as the place where I work is still on 4.3.0 and while they say it should work it is not supported. We just got the bits as we are supposed to update to 5 soon.
To get these bits your going to have to get it from your client if they want you to work with it. That would be my opinion other than that your best bet would be to contact Tibco to see if you can work something out.
The big question though will be what version of Tibco EMS your client is using.