Web Services: Difference between revisions

From DataFlex Wiki
Jump to navigationJump to search
m
Extending
(Cat WIP)
m (Extending)
Line 14: Line 14:


==VDF Implementation==
==VDF Implementation==
Within Visual DataFlex, Web Services are implemented through two mechanisms: one for creating '''services''' and the other for creating '''clients'''.
Within Visual DataFlex, Web Services are implemented through two mechanisms: one for creating '''services''' and the other for creating '''clients''' of existing services.


===VDF Web Services===
===VDF Web Services===
Line 21: Line 21:
In the Web Service Object (which will have a source file extension of ".wo") you then create methods ([[Function]]s and/or [[Procedure]]s), which you will subsequently [[Web_Service_Basics#Publishing_an_Operation|publish]] as your service's '''''operations'''''.
In the Web Service Object (which will have a source file extension of ".wo") you then create methods ([[Function]]s and/or [[Procedure]]s), which you will subsequently [[Web_Service_Basics#Publishing_an_Operation|publish]] as your service's '''''operations'''''.


By default [[Visual DataFlex]] publishes [http://www.ibm.com/developerworks/webservices/library/ws-docstyle.html Document Style] web services and unless you have a pressing reason to use the alternative ([http://en.wikipedia.org/wiki/Remote_procedure_call RPC] Style) you should adhere to this.  This means that, except in the simplest cases (such as the much-cited example of serving up a stock price), you will need to [[Web_Service_Basics#Defining_XML_Documents|define the documents]] which are to be passed to and from the service's operations.
By default [[Visual DataFlex]] publishes [http://www.ibm.com/developerworks/webservices/library/ws-docstyle.html Document Style] web services and unless you have a pressing reason to use the alternative ([http://en.wikipedia.org/wiki/Remote_procedure_call RPC] Style) you should adhere to this (it can be changed by setting the ''peSoapStyle'' property to ''ssRPC'').  This means that, except in the simplest cases (such as the much-cited example of serving up a stock price), you will need to [[Web_Service_Basics#Defining_XML_Documents|define the documents]] which are to be passed to and from the service's operations.  These are defined as extended data-types - structs and arrays - which can be combined to produce documents of arbitrary complexity.  


===VDF Web Service Clients===
===VDF Web Service Clients===


===Further Topics===
* Synchronous vs. Asynchronous
* Granularity
* Loose Coupling
* Reliablility
* Security
* Management
* Orchestration (what tom-cats hate! <g>)
* Choreography
* Composition
* Taxonomies and Semantics


----
----

Navigation menu