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

Post a Comment

Popular posts from this blog

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.
4 comments
Read more

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.
Post a Comment
Read more

70-562 Custom Visualizers

Framework objects are clearly viewable in the locals window during debugging. User made class librairies and their object need to provide visualizers for maintenance and debugging. You can create your own visualizers, MS exposes the functionnality through the .Net Framework; and this is relatively easy. Mulitple visualizers can be created per type. You can have tree views, grids; customizing it to the way that is the most usefull for debugging this particular object. The [Serializable()] attribute has to be included to your class to allow the visual studio visualizer to parse the object. A visualizer is a dll, a regular assembly, it requires a windows form to display the data. The visualizer class will be implemented by the form. The visualizer class has to inherit the DialogDebuggerVisualizer class with the DebuggerVisualizer attribute, and also the Microsoft.VisaulStudio.DebuggerVisualizers namespace. The visualizer can be made to only read, or modify existing data. T...
Post a Comment
Read more