Re: [Edbrowse-dev] mailx, plugin commands, mime, new sourcefile

[Adam Thompson <arthompson1990@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 5031 bytes --]

On Sun, Apr 12, 2015 at 04:46:08PM -0400, Karl Dahlke wrote:
> > Are we using a head request for http to determine this?
> 
> I never issue a head request, primarily because I don't need to 95%
> of the time, and I never know when that other 5% is coming.
> You pointed out, rightly so, that foobar.php can crank out
> anything, usually it's just another web page,
> wherein head would be a complete waste of time,
> and maybe quite a bit of time if that php program did a lot of computatio
> to get you to that next web page.
> Maybe it even ordered something for you through amazon,
> and issuing the command twice would order the item twice.
> I don't know but messing with head commands scares me.

Fair enough, it's tricky and on further reflection I can see the validity of
your arguments.
> > I ask as in some situations I can think of,
> > re-invoking the player with the URL once downloading has began may break things
> 
> Yeah I get that. That could happen.
> Not sure what to say about that.
> The edbrowse abort happens during the headers, not after,
> and that's a worst case,
> assuming it isn't redirected earlier by protocol,
> but if/when this happens
> most likely it would just look like a reconnect and not cause any trouble.
> It's even a connect from another program, another local port,
> so probably wouldn't be a problem.

May be, it depends on how the content distribution network works. I think we're usually ok with our current mechanism so that's fine with me.

> > I'd also be in favour of some sort of protocol set up
> > which would hand off URLs to external programs,
> > for example rtsp may be handed to mplayer for playing.
> 
> This is already done and has worked for quite some time.
> Look at this mime descriptor from my config file.
> It's also in the sample config file in the doc directory.
> 
> mime {
> #  the < forces it to be a stream, hence the url is passed to the program directly
> type = <audio/x-pn-realaudio
> desc = streaming audio
> suffix = rm,ra,ram,pls
> content = audio/x-scpls
> protocol = rtsp,pnm,sdp
> program = /usr/bin/mplayer -quiet
> }
> 
> The content = attribute is supported with the latest version,
> that wasn't there before,
> but it's there now and mostly works, and the other stuff worked before
> and would pass the url along based on protocol or suffix.
> This reminds me I need to reinstall mplayer, it's not on my new system.
> Guess I don't listen to real audio very often.
> I never got nasa real audio to run through mplayer,
> and that bums me out cause it's not on cable any more and I
> don't have any way to listen to space launches or coverage etc.
> But I digress.

Thanks for pointing out the protocol mechanism;
I see that most of the attributes aren't necessary,
but I'd like it if the type attribute was optional in the case that the
protocol attribute is provided.
I'd also probably rename this as plugin since it's now more than just mime type handlers.
For example:
plugin {
protocol=rtmp
program=flvstreamer
desc=rtmp streaming content
}
(I'm not sure about the exact flvstreamer options to get this to do anything sensible).
In this case type doesn't really apply, but name would and so does description.

> > I'd also like a pga option for plugins ask
> 
> Yes that's a good thought.
> We should think about this one for a bit.

Thanks, you're right this needs thought.

> I added mime.c, a new sourcefile, because well it just makes sense.
> I couldn't make any progress with little chunks of mime and plugin code
> scattered all through the files.
> So I gathered them together in mime.c, almost 300 lines of code,
> and it will grow quite a bit I'm sure as we develop this important capability.
> git pull and you'll see the new sourcefile.

Should this be plugin.c rather than mime.c?

> The behavior of edbrowse is still mostly as it was before,
> I've just made foundational changes,
> but now I can make some real changes / improvements.

Sounds good.

> > Actually, I think even Windows provides ways for you to override the defaults for things.
> 
> Sure they do, now, after the law suit,
> so they have to allow users to use maybe explorer + eudora, or perhaps firefox + outlook.
> Naturally they wanted to keep you locked into their software only and forever,
> but that wouldn't fly.
> But I digress.

Can we avoid the same locking in of users? I'd prefer it if we could.

> > Could you demonstrate this by *not* starting a new thread when you
> > reply to this email (and all emails actually);
> 
> Ok this is a test case, it should thread up with your mailx email.
> I did change the subject but I don't think that matters.
> If this worked I'll make it part of my regular procedure for communication
> on this list.

Yes, this works fine in my email client,
though the change of subject confused the googlemail web interface (which
apparently doesn't quite do threading properly).

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]