in recent times, service oriented architectures (soa) have become synonymous with web services, in which large enterprise systems communicate business-critical information. however, in this series of articles, we look at soa as a wider design principle that can be applied to any distributed object-based system--casting the net wider to include devices that sit at the edge of the network, both fixed and mobile.
introduction 【程序编程相关:我的Java开发之路】in this first article, we describe how we have taken soa onto mobile devices and show how to implement a simple messaging application using mobile soa design principles and point to some of the security implications and how to handle them. 【推荐阅读:JAVA的入门基础一些精典】
but instead of climbing into that particular bear pit--we arent going to try to argue which technology is preferable--we will be concentrating on some of the design patterns applicable to soa and how these can be applied to java devices both on the move and for fixed clients that need to access business services. 【扩展信息:Java平台乱弹二】
web services are just one of many possible implementation of the wider soa model. other more mature technologies, such as rpc, corba, rmi and jini have also been used as highly efficient "connection" technologies on which to implement large-scale, soa-based systems, and in fact many developers working with those technologies argue that theirs was the original platform for service-oriented architecture.
backgroundjava mobile technology is now mature and is available on millions of cellular phones around the globe. this profusion of java on the phone was initially led by a few far-sighted members of the java team at sun, and then by groups of like-minded people within the handset and device manufactures around the world who took up the job of getting small (sometimes tiny) devices to run a subset of the java technologies available on desktop and server machines.
... 下一页