VWG Communication between sessions and mashup capabilities

Hi All,

I wanted to hear your thoughts about a few features that we are contemplating on integrating to VWG.

We have recently been receiving more and more issues that could have been solved by enabling communication between sessions and the embedding of VWG forms in existing applications. We have even been challenged with some projects which needed real time messaging and updating to their clients. These features in many cases come in a combination which means that a project needs both real time updating and communication between sessions.

Some of the usages of such features would be as following:

1. Chats or real time messaging to other users.
2. Updating clients by push and not by pull (real time data updates such as inboxes, work items, statuses, locks, notifications and etc.)
3. Integrating VWG applications to other applications using simple JavaScript code (link integrating google maps into existing sites). A sample usage might be creating a spell checker which can be consumed from any site or a user search which is integrated to a backend system.
4. Real time administration of user rights and access permissions (admin will be able to throw a user out of the application).

What we had in mind is implementing all these features above a communication layer which will enable messaging between user sessions, the client and the server and hosting applications.

One limitations that will have to be solved is the web architecture entails client pull with no server push capabilities. We can see from implementations like google chat / facebook chat and more that this limitation can be overridden. The communication level will come in several flavors which in its enterprise version will enable to distribute the communication services across multiple servers and use a provided database as its messaging storage. In the simplest solution we will use an application level storage which will enable to use these features with out resorting to full blown server farm scenario.

Another limitation is cross domain AJAX which has been resolved by yahoo, google and etc. by using REST (pure javascript) interactions. This also enables implementing real time solutions by calling the server and halting the response until there is a message available for the client. This is how google / yahoo and etc. implement there real time capabilities.

We would be happy to hear your thoughts about these capabilities and the proposed implementation.

How these features might help you?
What scenarios will you be interested in implementing using these capabilities?
Is real time messaging / updating, is something you need?
Do you require the ability to launch forms using plain script from other sites?
Would a central system which is binded to other systems and its forms can be embedded in other applications provide you any benefits?

Thanks,
Guy