Skip to main content

70-562 Web Services


A single server can't handle it all, connecting many computers together is far more powerfull than in a mainframe.

In distributed applications, One cluster may be for the database, then a group of servers might function as a specialized application server, and still others handle user interface and security logic.
All those computers need to communicate together.

There are 4 broad WS technollgies,
1) Universal access: The tcp/ip is most common protocol
2) Standard data representation: xml is intended to transport data. And XPath that allows to xtract a subset of data easily, while http was made for to transport markup(html). While
3) Standard message format: SOAP stadardizes the message envelope
4) Service description format: WSDL web services description language

The web service has to derive from System.Webh.Services.WEbService and contain the WebSErvice and WebSErviceBinding attribute.
The WebMethod attribute is added to each methods exposed to the outside world.
The http://tempuri.org is a placeholder, you can put one of your own, there is not repository keeping track of it, it doesn't need to be browsable, it's just an id to uniquely identify like a guid would do.
Must be constant over time: versioning.
Use datasets or custom objects(serialized).
Chunky is better than chatty, sending a big chunk of SOAP is better than a bunch of little chunks.

The client has to capture the types and web methods, this is done by adding a service reference to the client project, this is when the wsdl file is generated.
Visual Studio creates a proxy class that will handle the request and response.

The disco file contains the location of the wsdl file, the client uses this file, the discomap maps both wsdl and disco file togther.

WCF: Contract is a key concept, the client and the server agree wont change.
DataContract is used to identify types.
ServiceContract defines the service, usualy defined as an interface.
The svc file provides the service host, in a command line application this one would need to be created manualy. To test the service availability, invoke this svc file in the browser.
WCF is a topic in it's own, this just scratch the surface, but is all that is needed as far as 70-562 goes.

Comments

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.