Domicel Q & A

Correct me where I'm wrong

Q:

So, if I'm reading this correctly, basically you are providing an architecture whereby an application vendor can write an interface to their custom app which will expose its methods via web services in a distributed environment?

These web services once exposed have awareness of each other due to the common architecture framework, and can each invoke each others methods, if they have appropriate access?

So that for instance if I were editing a document, I could invoke a spell checker, which would be supplied by a vendor web service and already configured to spell check my document. In a fashion reminiscent of the way Firefox allows you to write extensions to add custom search engines to your browser, only in this case the extensions could "talk" to each other as well, and not just the browser??

Correct me where I'm wrong.

A:

You got it!

But that's not the interesting part. What you described can already be done via Web Services, etc.

What Domicel adds is multi-multitenancy. Multitenancy refers to the ability of one application to support many users and keep track of each user's activities separately. Domicel enables many applications to do the same thing together, without explicit support from the programmer. All the programmer has to do is support a simple interface.

This interface, by the way, makes it easier to write large applications, because the same solution can be applied to different parts of the same application.