Sorry that I didn't get chance to reply. Tend to forget things after the rare long weekend.
What I've found is that GDS rejects search request coming from browser plugins. From the network packets, the ActiveX control on IE closes the TCP connection right after the connection is established. My guess is GDS hooks into the winsock lib and close the connection from the client side. I could call an external app from the ActiveX control which seems to go through. Or running a standalone app should also work. But these all pose problem for deployment, so for now, we decide to hold on using GDS. Thanks for your help. Roy On Jul 3, 8:19 pm, "Benjamin [API Guru]" <[email protected]> wrote: > I think IE Control or Firefox Plugin should be possible. Your plugin > would need access to the users registry to get the query token and > then work as a proxy to search the local machine. > > There are some issues you might want to think about: > a) You will have to maintain a plugin for every browser in use which > probably means one plugin for IE, one for Firefox/Chrome/Opera/Safari > (I think they use the same architecture). > b) Security issues since the plugin is available for all webpages (you > don't want another page to query your index without permission) > c) Installation/Update routines to keep the machines which use the > plugin up-to-date and stay in sync with possible architecture changes > in the browsers. > > When using a separate application: > a) You will only have to maintain one application > b) If you just listen on the lan address no external webpage can > access your machine. You could even filter access just by the server > IP > c) You can roll out the application with a custom setup and maintain > it like any other app on the network. > d) You will have some latency since the data will go through the > server for every query which will depend on the connection and network > usage. > > I guess both ways would work and it probably depends on how much time > you want to invest in the project and maintenance of it. > > Another option could be a signed Java applet. I think a signed applet > can access the registry but I am not sure. The applet would be > independent of the browser and operating system so you would have to > only maintain one applet. > > Best regards, > Benjamin > > On Jul 2, 6:57 pm,Roy<[email protected]> wrote: > > > > > Hi Benjamin, > > > First thanks for the explanation. I'm aware of the same origin policy > > and the branding requirement from GDS. > > > What if I issue the search through browser plugin, e.g., ActiveX > > control(IE) or Plugin(FF)? Is that possible? > > > Thanks > > >Roy > > > On Jul 2, 7:33 am, "Benjamin [API Guru]" <[email protected]> > > wrote: > > > > Plugins are not exposed to the web browser. The plugins are able to > > > use ActiveX objects for advanced features. > > > > To search the index you can use the Query API. However, due to > > > security restrictions, search queries can only be issued from the same > > > machine Google Desktop runs on (Since it only listens on localhost). > > > If you want to search a Google Desktop search index from another > > > machine you would have to develop a proxy application that listens to > > > search requests and forwards them to Google Desktop. Searching > > > directly from within the browser using Javascript is not possible > > > because of the same-origin policy, which only allows XMLHttpRequests > > > to the same domain on which the Javascript is run, and I think this > > > includes the port (so Google Desktop localhost is different than a > > > local apache webserver). > > > > Searching the local machine should be possible if you > > > a) Have a proxy application running on every machine > > > b) Send the machine IP to the server with the search query > > > c) Issue the search request from the server, through the proxy on the > > > machine to Google Desktop > > > d) Return the results from the server - maybe processed to match the > > > layout > > > > I'm not sure if this applies (since this might only be used > > > internally) but you might also bound by the Branding > > > Guidelineshttp://desktop.google.com/dev/brandguide.htmlforyourquery and > > > results pages. > > > > Best regards, > > > Benjamin > > > > On Jul 1, 8:25 pm,Roy<[email protected]> wrote: > > > > > GDS query API supports native plugins and scripting plugins, so it > > > > gives me the impression that the plugins are exposed to web browser. I > > > > thought in IE I could create an ActiveX control then use javascript to > > > > send search query to the localhost. Yet it doesn't seem to work. > > > > > Is this possible? Am I heading the wrong direction? > > > > > If not, what are the options out there? I basically need to search the > > > > machine that the web browser runs. The server is not on the > > > > localhost. > > > > > Thanks > > > > >Roy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Desktop Developer Group" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Desktop-Developer?hl=en -~----------~----~----~----~------~----~------~--~---
