[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] GSoC Project | Design and Implementation of a Framework f
From: |
Tim Ruehsen |
Subject: |
Re: [Bug-wget] GSoC Project | Design and Implementation of a Framework for Plugins |
Date: |
Tue, 21 Mar 2017 10:58:57 +0100 |
User-agent: |
KMail/5.2.3 (Linux/4.9.0-2-amd64; KDE/5.28.0; x86_64; ; ) |
On Tuesday, March 21, 2017 2:29:20 AM CET Didik Setiawan wrote:
> On Mon, Mar 20, 2017 at 04:15:44PM +0100, Tim Ruehsen wrote:
> > Welcome, Didik !
>
> Thanks, Tim.
>
> > One way to implement plugins is via libdl (dlopen(), ...), and that is
> > what I have in mind. That is not perfectly portable, but our first goal
> > will be systems that support dlopen().
>
> So, should I continue to use dlopen() or there is another better method? In
> case we need more portability.
>
> > Since we can't (or want) to make everything pluggable, we should first
> > address the already requested functionality. There should be (some ?)
> > requests in the wget1.x issue tracker that ask for plugin / external
> > program for some good reasons. You should review these, pick the parts
> > that seems reasonable to you and implement these first.
> >
> > E.g. I remember someone asking for some customisable 'filter' for URLs to
> > follow. In terms of a loadable module, that would be a function that takes
> > a URL and returns 1|0 (yes|no). Or a bit more general: takes a URL plus
> > extra information, e.g. referer, host, mimetype, ... and maybe returns a
> > list of URLs to fetch. Whatever makes sense.
>
> Do you talking about this [1]? Then I refer to one of the three idea that
> says call an external program which returns 0 or 1 to signal acceptance or
> rejectance of each proposed URI. Wget shall wait for the program to return.
> Any other exit status shall cause wget to terminate.
> I will try to implement this.
Hi Didik,
please, don't start coding yet. The application period is not over (deadline
3rd April). During 3-24 April we (the mentors) will review all applications
and then decide who will be accepted.
Work on a proposal about the plugin feature - feel free to discuss details or
ask questions.
Give us a good impression by starting small works on the code base / testing /
create issues / whatever (see also the answers to Avinash's questions about
what to do). Prove your skills.
Back to [1]: That seems what I meant, there are some good ideas that you can
take. Having a plugin system (BTW, @Eli is right by suggesting libtool), you
could implement using an external program by loadable plugin.
> [1] https://savannah.gnu.org/bugs/?45803
Regards, Tim
signature.asc
Description: This is a digitally signed message part.