火龙果软件Comparison_of_Web_Services__JavaRMI__and_CORBA_service概要1.pptVIP

火龙果软件Comparison_of_Web_Services__JavaRMI__and_CORBA_service概要1.ppt

  1. 1、原创力文档(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。。
  2. 2、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  3. 3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
  4. 4、该文档为VIP文档,如果想要下载,成为VIP会员后,下载免费。
  5. 5、成为VIP后,下载本文档将扣除1次下载权益。下载后,不支持退款、换文档。如有疑问请联系我们
  6. 6、成为VIP后,您将拥有八大权益,权益包括:VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
  7. 7、VIP文档为合作方或网友上传,每下载1次, 网站将根据用户上传文档的质量评分、类型等,对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档
查看更多
火龙果软件Comparison_of_Web_Services__JavaRMI__and_CORBA_service概要1

Configuring stateful service Deployment switches for .Net, Apache SOAP, and JAXRPC systems – both client and server side. With JAXRPC server in Tomcat Implementation class supports second interface which has hook functions allowing access to Tomcat’s servlet session variables Stateful web service Session context provides hash-map like structure for storing named data objects “Calculator” illustrative example in paper Code Ugly if actually store state variable in “session context” Cleaner if actual implementation object (and its internal state) are stored as session state for a Web Service object that acts as a proxy Analogies WS implementation like CORBA “tie” class Possibly better analogy with CORBA POA-locator Session key (from cookie) acting as object-id WS class locates instances of corresponding business object and invokes method Stateful iterator Typical CORBA usage wouldn’t return large sequence like that needed for “large data” example – instead would have reference to stateful iterator returned. Easy to implement a WS analogy with simple stateful iterator as session variable One practical effect – WS client no longer more memory demanding than CORBA client Deployment Deployment and stability Not initially one of aspects to explore Possibly the best reason to swap to a Web Service style implementation! Web Service Service packaged as servlet to run in Tomcat or similar Auto-generation of all web.xml deployment files Tomcat Easy to administer Persistent configuration and deployment data Auto-restart Hot substitution and addition of code Lots of experienced administrators CORBA – 2nd CORBA daemon (e.g. orbd) Persistent name service Restarts servers when required Relatively easy to use Less likely to have experienced administrator Java RMI Server side: rmiregistry HTTP server handling class file distribution Services must be pre-launched Alternatively, even more complexity with rmid No persistent configuration data Fragile Complicated (rules regarding locati

文档评论(0)

676200 + 关注
实名认证
文档贡献者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档