Supporting custom schemes is actually an interesting feature, if so someone can implement programs to handle various protocols, like Telnet/SSH client within Chrome. There is a Firefox extension can handle telnet connections. This would be a nice feature for Chrome OS :)
On Nov 21, 5:48 am, Aaron Boodman <a...@google.com> wrote: > Messaging through the DOM is the best way to do that now. We > eventually want to expose chrome.extension.connectExternal() to all > web pages, and you could use that to message to an extension. > > - a > > > > On Fri, Nov 20, 2009 at 11:48 AM, Karen <karent...@gmail.com> wrote: > > We're using them to communicate between our website to the addon, > > without having to message through the current DOM. > > > Our website just has to call > > > foo://showPrompt > > > and we have a corresponding handler in our addon's javascript that > > listens to the foo channel and shows a prompt. > > > On Nov 20, 2:37 pm, Aaron Boodman <a...@google.com> wrote: > >> Well, those interfaces are very broad. What are you using them for? > >> Perhaps there is a way to do something similar in Chrome. > > >> As an example, sometimes people use these interface to implement their > >> own protocol, just do display UI in the tab contents area. You can do > >> this in Chrome other ways. > > >> - a > > >> On Fri, Nov 20, 2009 at 11:12 AM, Antony Sargent <asarg...@chromium.org> > >> wrote: > >> > No, we don't support this. > > >> > On Fri, Nov 20, 2009 at 9:04 AM, Karen <karent...@gmail.com> wrote: > > >> >> Wondering if there's a way to implement our own protocol scheme like > >> >> there is in Firefox--these are the current interfaces we're using to > >> >> do so: > > >> >> const kSIMPLEURI_CONTRACTID = "@mozilla.org/network/simple-uri;1"; > >> >> const kIOSERVICE_CONTRACTID = "@mozilla.org/network/io-service;1"; > >> >> const nsISupports = Components.interfaces.nsISupports; > >> >> const nsIIOService = Components.interfaces.nsIIOService; > >> >> const nsIProtocolHandler = Components.interfaces.nsIProtocolHandler; > >> >> const nsIURI = Components.interfaces.nsIURI; > > >> >> -- > > >> >> You received this message because you are subscribed to the Google > >> >> Groups > >> >> "Chromium-extensions" group. > >> >> To post to this group, send email to > >> >> chromium-extensi...@googlegroups.com. > >> >> To unsubscribe from this group, send email to > >> >> chromium-extensions+unsubscr...@googlegroups.com. > >> >> For more options, visit this group at > >> >>http://groups.google.com/group/chromium-extensions?hl=. > > >> > -- > > >> > You received this message because you are subscribed to the Google Groups > >> > "Chromium-extensions" group. > >> > To post to this group, send email to > >> > chromium-extensi...@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > chromium-extensions+unsubscr...@googlegroups.com. > >> > For more options, visit this group at > >> >http://groups.google.com/group/chromium-extensions?hl=. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Chromium-extensions" group. > > To post to this group, send email to chromium-extensi...@googlegroups.com. > > To unsubscribe from this group, send email to > > chromium-extensions+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/chromium-extensions?hl=. -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=.
