The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Nov. 10, 2009
Filed:
Nov. 30, 2004
Matthew D. Joe, Issaquah, WA (US);
Paul C. Currit, Issaquah, WA (US);
Minn Thein, Issaquah, WA (US);
Sumit Chawla, Bothell, WA (US);
David Mainer, Seattle, WA (US);
Stephen J. Maine, Seattle, WA (US);
Christopher Chang, Redmond, WA (US);
Mei Yuei Lee, Redmond, WA (US);
Kyle F. Huntley, Lake Forest Park, WA (US);
Karel Deman, London, GB;
Blake M. Dong, Rowland Heights, CA (US);
Matthew D. Joe, Issaquah, WA (US);
Paul C. Currit, Issaquah, WA (US);
Minn Thein, Issaquah, WA (US);
Sumit Chawla, Bothell, WA (US);
David Mainer, Seattle, WA (US);
Stephen J. Maine, Seattle, WA (US);
Christopher Chang, Redmond, WA (US);
Mei Yuei Lee, Redmond, WA (US);
Kyle F. Huntley, Lake Forest Park, WA (US);
Karel Deman, London, GB;
Blake M. Dong, Rowland Heights, CA (US);
Avanade Holdings LLC, Seattle, WA (US);
Abstract
A prescriptive architecture for application development is provided. In some embodiments, the architecture comprises a service, a receiver, a sender, and a transport. The service functions to perform the actual business logic, is decorated with service deployment metadata; and is operable to communicate via types. The receiver is coupled to the service and is generated entirely from the service deployment metadata. The receiver is operable to receive messages, convert the received messages into types, and communicate with the service using the types. The sender is coupled to the receiver and is generated entirely from the service deployment metadata. The sender functions as a proxy for the service to a service consumer, and is operable to communicate using types with the service consumer. The sender is operable to convert the types to messages, and communicate with the receiver via messages. The transport functions as a message exchange technology that allows the sender and receiver to communicate, and is designated by the service deployment metadata and implemented as an underlying technology of the sender and the receiver.