soa

I want to use asymmetric encryption of headers in RESTful requests to verify the identity of the system sending the request: i e System A encrypts it's name, timestamp, and the service name using it's public key in a request to System B. System B then uses the public key of System A to decrypt, proving the authenticity of the request. 1) Does php-mcrypt support this? 2) Has anyone benchmarked this type of operation? No, mcrypt is just symmetric block ciphers. However the PHP OpenSSL extension supports asymmetric operations. The ones you want are openssl_sign and openssl_verify . (You have a

软件体系结构研究新方向 21世纪软件技术展望 1.开放源代码 下一世纪的操作系统将继承现在好的操作系统的主要优点，变成开放的和进化的。在操作系统开放之后，系统软件产业将主要集中在软件环境平台和工具的研究开发上。可视化编程环境与工具、办公套件、家庭套件、学习套件等将会有很大的空间。 21世纪软件技术展望 2.跨平台 使得一次写好的应用软件在各种不同硬件系统上都可以运行、使得已经设计好的程序模块被有效地重复利用。 目前跨平台这一设想还没有完全有效地被实现，相信21世纪第一个10年一定可以完成。当然，如何解决非Java语言软件的跨平台问题仍然是一个难题。 21世纪软件技术展望 3.软件工业化 随着软构件的规范化和实用化，计算机软件生产的工业化程度会慢慢提高，软件发展的速度也会慢慢加快。估计到21世纪的第一个10年结束的时候，软件的工业化程度应该达到20世纪90年代中期计算机硬件的工业化程度。 21世纪软件技术展望 4、友好界面 多媒体技术、语音识别与合成技术、手写体文字的识别、自然语言理解与机器翻译技术、图像处理与图形学技术、用户图形界面技术、人工智能技术等等都是解决软件系统友好性的关键技术。 21世纪软件技术展望 5.基于网络的应用软件 利用了WEB浏览技术、多媒体技术和网络信息管理系统等综合技术而构成的网络应用软件（例如电子商务）将是今后软件业发展的最大舞台。 纲要

What is the proper way to handle polymorphic business objects in a WCF/SOAP world? It seems to me that SOA and OOP are at odds with each other - to expose a clean WSDL you need concrete objects, typically not even utilizing inheritance. On the other hand, presumably in the underlying system, you'll want to follow proper OO design. What do people typically do here? Build a set of WCF contract objects, forgoing OOP principles, then convert to and from another set of objects in the actual logic layers? What do people typically do here? Build a set of WCF contract objects, forgoing OOP principles,

部署开发，需要三部分：服务提供者、服务容器、服务消费者 本人用 eclipse 开发 1、服务提供者jar生成 A、项目截图 B、源码： package com.alibaba.dubbo.demo; public interface DemoService { String sayHello(String name); } package com.alibaba.dubbo.demo.provider; import com.alibaba.dubbo.demo.DemoService; public class DemoServiceImpl implements DemoService{ public String sayHello(String name) { return "Hello " + name; } } provider.xml <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dubbo="http://code.alibabatech.com/schema/dubbo" xsi

From my understanding JSONP can only be achieved using the GET verb. Assuming this is true which I think it is, then this rules out core compliance with true REST in which you should make use of different verbs i.e. GET,PUT,POST,DELETE etc... for different and specific purposes. My question is what type of barriers am I likely to come up against if I were to say allow updating and deleting of resources using a JSONP service using a get request. Is it better practice to offer a JSON service and state that the user will need a server side proxy to consume using JavaScript XDomain? Cheers ,

Lets assume that I'm dealing with a service that involves sending large amounts of data. If I implement this with WCF, will WCF throttle the service based on how much memory each request takes to serve? Or will I be getting continuous out of memory exceptions each time I receive a large number of hits to my service? I'm quite curious as to dealing with this problem outside of WCF, I'm still a bit new to service development... While using the binding attributes and readerQuotas like Andrew Hare suggests will allow for essentially an unlimited size for most practical uses, keep in mind that the