[gopher] [Gopher Clients]: Chrome Extension

[James Mills]

On Tue, Dec 16, 2014 at 11:21 AM, Cameron Kaiser <spectre at floodgap.com>
wrote:

> That's correct (at least with respect to the URL bar). Look at the source
> for
> how I got around that. It was a big kludge but it mostly worked.
>
> Once you have control of the page, such as forwarding it to a chrome URL
> under the control of the extension, you should be able to open a socket and
> perform menu parsing and display.
>

So in other words the schema part of the URI
would still have to be "hacked up" but at least
now we can open up raw TCP sockets
and have better control of the underlying comms?

cheers
James


James Mills / prologic

E: prologic at shortcircuit.net.au
W: prologic.shortcircuit.net.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20141216/ecdcad47/attachment.html>