That does help, Thanks Chris.

On Oct 15, 7:34 pm, "Chris Prince" <[EMAIL PROTECTED]> wrote:
> Thanks for asking, Alan.
>
> Gears probably isn't the best choice for this.  The question has come
> up a couple times before, and the consensus is that security issues
> are a blocker for interfacing with arbitrary external hardware.
>
> Hope that helps,
> --Chris
>
> On Wed, Oct 15, 2008 at 3:26 AM, Arctic Giraffe
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hi,
>
> > I'm afraid I know nothing about Gears but could do with an answer to
> > my question below to work out if it's worth going further with the
> > Gears route of development.  Apologies if this turns out to be a
> > 'stupid question'.
>
> > I have a hardware peripheral that I want to use to interact with a web
> > server.  I have binaries for the peripheral and an accompanying API in
> > the form of a MS Visual C++ project which I'd like to use.
> > The question is: Is it possible to implement this interaction between
> > an external windows application (built using MS Visual C++) and a web
> > application made with Gears?
>
> > Some basic requirements I have for this interaction are listed below.
>
> > 1. Ability to open a web browser - start web application
> > 2. Ability to transfer data between hardware peripheral and web
> > application
> > 3. Ability of the web application to call routines on the hardware
> > peripheral through the windows application running it.
> > 4. Ability of the hardware peripheral windows application to call
> > routines in the Gears web application.
>
> > I assume there are some clever security features in Gears that might
> > well prevent this?
>
> > I would be very interested to hear any recommendations of alternative
> > approaches if Gears is not appropriate.
>
> > Thanks for reading,
>
> > Alan

Reply via email to