Hello, I'm currently considering using Gears as a way to accomplish cross- domain messaging. While the majority of users will be browsing and exchanging data from a Gears-capable browser on a Gears-supported platform, I would also like to exchange messages with an embedded device running an RTOS.
This device has a web server and an IP stack, but is too resource- constrained to run the entire Gears framework, and would only use the WorkerPool features anyway. My question is regarding a WorkerPool API for message passing. If I understand the WorkerPool concept correctly, I can add a remote Worker to a client-side WorkerPool, and access data from the LocalServer or Database on the REMOTE server. This suggests to me that any requests for LocalServer content, or queries to the database must first be translated to an HTTP request, that is sent to the remote client hosting the Worker spec. My hope is to provide the javascript file for the remote worker from the remote webserver, and intercept any HTTP requests sent from a client. I can then format the response to these requests so it appears that there is a worker functioning at the remote client. To summarize: Given a client using a Gears-capable browser, and a remote HTTP stack, is there a way to send a message from the client to the remote server, and receive a message as if it were sent from a remote Worker? Thanks in advance for any help!
