Technique for enabling a plurality of software components to communicate in a software component matrix environment

1. A method for enabling a plurality of software components to communicate in a software component matrix environment, the method comprising the steps of:

encoding a request at a handler at a client side;

communicating the request to a server at a server side via a communication interface;

comparing the request to a plurality of operations supported at the server side;

determining whether a function match exists at the server side; and

returning a response comprising the function match to the client side in response to the request via the communication interface wherein the response is mapped to a data model of a client.

2. The method of claim 1 , wherein the function match is an exact match.

3. The method of claim 1 , wherein the step of determining whether a function match exists further comprises the step of:

filtering at least one association associated with the request wherein the function match is a close match to the request.

4. The method of claim 1 , wherein the step of determining whether a function match exists further comprises the steps of:

calling a general query; and

implementing a generic interface when no function match exists.

5. The method of claim 1 , wherein a generic data structure abstracts an interface from the client side for inserting at least one capability into a generated application program interface object wherein the object possesses one or more of an event auto-registration function and an event auto-trigger function.

6. The method of claim 1 , wherein the communication interface further comprises an iterator adjusting a data rate across the communication interface by sending one or more chunks of data of an optimal transfer size.

7. The method of claim 1 , wherein a cache on the client side comprises a configurable persistent write through buffer allowing at least one change on one of the client side and the server side to be reflected on both the client side and the server side.

8. The method of claim 1 , further comprising the step of:

interpreting communication sent from a client side handler to locate one or more servers for client communication and determine one or more communication interface types.

9. The method of claim 1 , wherein the request is in extensible markup language.

10. A system having a computer and memory for enabling a plurality of software components to communicate in a software component matrix environment, the system comprising:

one or more computers with memory;

instructions stored in the memory providing a handler for encoding a request at a client side; and

instructions stored in the memory providing a server object for communicating the request to a server at a server side via a communication interface; comparing the request to a plurality of operations supported at the server side; determining whether a function match exists at the server side; and returning a response comprising the function match to the client side in response to the request via the communication interface wherein the response is mapped to a data model of a client.

11. The system of claim 10 , wherein the function match is an exact match.

12. The system of claim 10 , wherein at least one association associated with the request is filtered wherein the function match is a close match to the request.

13. The system of claim 10 , wherein a general query is called and a generic interface is implemented when no function match exists.

14. The system of claim 10 , wherein a generic data structure abstracts an interface from the client side for inserting at least one capability into a generated application program interface object wherein the object possesses one or more of an event auto-registration function and an event auto-trigger function.

15. The system of claim 10 , further comprising an iterator for optimizing a data rate produced across the communication interface.

16. The system of claim 10 , further comprising a cache on the client side comprising a configurable persistent write through buffer for allowing at least one change on one of the client side and the server side to be reflected on both the client side and the server side.

17. The system of claim 10 , wherein implementing an auto server location algorithm is implemented for locating the server and determining a communication interface type.

18. A computer readable non-transitory storage medium containing code for enabling a plurality of software components to communicate in a software component matrix environment, the computer readable medium comprising:

instructions carried on the computer readable medium;

wherein the instructions are configured to be readable from the computer readable medium by at least one processor and thereby cause the at least one processor to operate so as to:

encode a request at a client side;

communicate the request to a server at a server side via a communication interface;

compare the request to a plurality of operations supported at the server side;

determine whether a function match exists at the server side; and

return a response comprising the function match to the client side in response to the request via the communication interface wherein the response is mapped to a data model of a client.

19. A computer readable non-transitory storage medium of claim 18 , wherein the request is in extensible markup language.