Show description

Alas, most folks are just not visionaries. Meanwhile, the people that got it started writing code. Large enterprises created their own definitions of what this XML should look like and how it was to be used to request services. Any group that knew how to use an implementation of the Document Object Model (DOM) could expose these services, or prepare requests for them and leverage the functionality. In 1999, a sharp young engineer read an obscure specification put out by an XML working group called SOAP.

When users want to see data, you cannot tell them that a request for the data they want to see has been submitted, and to come back later to see it. For synchronous requests for data, you use a simple timeout listener loop within the data access abstraction layer. This monitors an incoming MSMQ for a correlated result message, sent back from the queue listener when the work has been completed. This architecture makes it very easy to put in a timeout should the request take too long. This timeout period can (and should) be controlled by a configuration file.

Data must also be secured. You can secure data by encrypting it, or by keeping it in an otherwise secure data store. An opportune time for encryption is when you’re moving data around on the network, or sharing data with partners. Typically, when you’re done moving it around, you write it down in a source of persistence that keeps it safe for you, like within a relational database that requires credentials for access. NET. Table 1-2. NET Solution Do we know who you are? NET Forms-based security Active Directory IIS Passport Do we know you have permission to do what you’re doing?