public marks

PUBLIC MARKS with tag ws-*


InfoQ: WS-I closes its doors. What does this mean for WS-*?

by nhoizey
So the question remains: has interoperability pretty much been achieved for WS-* through WS-I and the improvements made with the way in which the specifications and standards are developed today, or has the real interoperability challenge moved elsewhere, still to be addressed?



The Cover Pages: ISO Publishes Three WS-I Profiles

by nhoizey
The Web Services Interoperability Organization (WS-I) today announced that three of its Profiles have been published by the International Organization for Standardization (ISO)

WSO2 Web Services Framework for PHP | WSO2 Oxygen Tank

by nhoizey & 2 others
WSO2 WSF/PHP is a complete solution for building and deploying Web services, and is the only PHP extension with the widest range of WS-* specification implementations


REST vs. WS-*: War is Over (If You Want It) :: David Chappell :: Blog

by nhoizey & 1 other
REST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security

SOA et Web Services : Questions / RÈponses

by nhoizey & 1 other
Des tonnes d'infos intéressantes sur SOA et les Web Services, par Pierre "Orchestra Networks" Bonnet

Forrester narrows list of specs for Web services

by nhoizey
"The place to really watch, if you're a conservative watcher and you don't want to watch much in the industry about these emerging specifications is WS-I," he said. "It's putting together answers to technical questions that people need answered if they want things to work together for Web services interoperability."

Radovan Janecek: Nothing Impersonal: Mental Exercise

by nhoizey
Is HTTP GET/POST enough for you? Fine. Then you are simply not the 'right target' for web services evangelists ;-)

Radovan Janecek: Nothing Impersonal: WS-Transfer and WS-Enumeration

by nhoizey
The WS-Transfer one is nice because it allows REST style of interactions.

Radovan Janecek: Nothing Impersonal: September 2004 Archives

by nhoizey (via)
Will there be still 97% of simple REST services on the web then? Yes, sure. WS-* does not compete with browser-oriented applications or simple-get-then-do-regexp interactions

Sam Ruby: Tolerance

by nhoizey (via)
acceptable levels of tolerance differ depending on whether or not a given operation is safe or not

by nhoizey (via)
to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!


The Cafes » REST vs. WS-*: A Parable

by benoit & 1 other
My name’s Rusty, and I’m an air conditioning tech.

PUBLIC TAGS related to tag ws-*

architecture +   attachment +   basic +   bpel +   clevermarks +   dev +   encoding +   esb +   framework +   groupe:clever-age +   interopérabilité +   iso +   logiciel_libre +   mda +   mtom +   php +   php5 +   profile +   qos +   rest +   securité +   security +   soa +   soap +   standard +   tolérance +   twitter +   type:slides +   unicode +   uri +   utf-8 +   vs +   web service +   web services +   web_services +   ws-i +   ws-security +   WS-Tranfer +   wsdl +   wso2 +   wsrp +   x.509 +   xml +   xml schema +   xsd +  

Active users

last mark : 22/11/2010 17:32

François Hodierne
last mark : 01/04/2009 06:09

last mark : 11/06/2007 06:52