JINI 还活跃吗？
与我交谈过的每个知道它的人都声称这是自切片面包以来最伟大的事情。 为什么失败了？ 或者，如果它没有失败，现在谁在使用它？
Everyone I talk to who knows (knew) about it claims it was the greatest thing since sliced bread. Why did it fail? Or, if it didn't fail, who's using it now?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
这个想法的事情肯定已经平息了。 这很奇怪，因为你会认为它的目标现在更加相关。
http://www.jini.org/wiki/Category:News
Things have definitely quited down for the idea. Which is strange since you'd think its goals are even more relevant now.
http://www.jini.org/wiki/Category:News
查看GigaSpaces。 这是一个相当成功的 Jini/Javaspaces 实现。
我认为 Jini 有一个很棒的模型，但它受制于 Java。 Web 服务更有吸引力，因为它与标准化协议一起工作，尽管 Jini 服务发现更自然。
Check out GigaSpaces. It's a quite successful Jini/Javaspaces implementation.
I think Jini has a great model, but it is stuck with Java. Web-services is more appealing because it works with standarized protocols, even though Jini service discovery is more natural.
老问题，但 JINI 被交给 Apache 并成为 Apache River 项目。 然而，该项目现已退役。
old question, but JINI was given to Apache and became Apache River project. However, that project is now retired.
Zeroconf 和其他发现协议同样被称为自切片面包以来最伟大的事情； 只是味道在不断变化。
Zeroconf and other discovery protocols are similarly referred to as the greatest thing since sliced bread; it's just that the flavor keeps changing.
我的两分钱... Jini 过去/现在都很好，但我认为，在当时公司开始不愿意为 CORBA 带来的东西支付大笔费用时，它试图成为一个以 Java 为中心的 CORBA。 WS-* 规范开始获得业界“公认的解决方案”的关注。 我认为 Jini 本来可以在一个小窗口中攫取大量市场份额，但它从未发生过。 与其他替代方案相比，Sun 对 Jini 带来的产品想要的钱太多了。 我很想听听不同意的人的意见！ 我的观点是，Jini 技术不错，但商业方面在企业中没有前途。 它可能会在其他地方找到一席之地，具体取决于甲骨文决定用它做什么。
My two cents... Jini was/is nice, but I think it tried to be a Java-centric CORBA back in the day when corporations were beginning to be reluctant regarding paying the big bucks for what CORBA brought to the table. WS-* specs began to acquire the "accepted-solution" mind-share in the industry. I think there was a small window where Jini could have grabbed substantial market share, but it never happened. Sun wanted too much money for what Jini brought to the table compared to other alternatives. I would love to hear from folks that disagree! My opinion is that Jini is sound tech, but business-wise has no future in the enterprise. It may find a niche elsewhere, depending on what Oracle decides to do with it.
Jini 是一项了不起的技术。 推动 EJB 系统的唯一原因是它允许 Sun 销售更多硬件，因为 EJB 在高性能机器上运行得最好（由于共享状态和数据库访问）。 当时（1999 年）Jini 允许更好的可扩展性，在商用硬件上运行良好，因此 Sun 不推广 Jini 是有道理的。 这是一个耻辱，因为我一直想知道什么时候有人会发布一个开源的易于使用的 Jini 服务器，就像 JBoss 在 J2EE 中所做的那样。 然而，我确实通过使用 Jini 技术（基于 Linda TupleSpaces）并通过使用以其他方式实现的元组空间将它们应用于编写软件系统，为公司节省了大量时间和金钱。
Jini was an amazing technology. The only reason pushed EJB systems was that it allowed Sun to sell more hardware as EJB ran best on highpowered machines (due to shared state and database access). At the time (1999) Jini allowed much better scalability which ran well on commodity hardware, so it made sense for Sun to not promote Jini. Its a shame as I kept wondering when someone would release an Open Source easy to use Jini server like JBoss did with J2EE. I did however save companies alot of time and money by using the Jini techniques (based on Linda TupleSpaces) and applying them to writing software systems by using Tuple Spaces implemented in other ways.
在我看来，Jini 皇冠上的宝石是它的 JavaSpaces 服务。 遗憾的是Sun似乎已经放弃了它。 它仍然以 Apache River 的形式存在，但现已退役。
The jewel in the crown of Jini was it's JavaSpaces service IMO. Sad that Sun seem to have abandoned it. It still exists as Apache River, but is now retired.