- snip ---
>
> So we need to maintain a handle per instance of the http filesystem
> (in principle nothing prevents the user to operate more than one http
> filesystem).
>
- snip --
>
> Note that the file interface callbac
In the init_fn I will need save a reference to libcurl for use in a
variety of functions during normal runtime. My instinct is to have
a pdf-fsys-http.c scoped static structure to store this, and a
couple other items in. This will make it accessible to all my
functions without any
> I pushed a patch providing support for both init_fn and cleanup_fn.
> Note that the filesystem state created at init_fn time is only
> available at cleanup_fn time. If you need to access the state in some
> of the other filesystem implementation functions we will need to add a
> new parameter to
> And then call those callbacks in the existing pdf_fsys_create and
> pdf_fsys_destroy. Stateless filesystems (such as the disk filesystem)
> would not define those callbacks.
>
> Would this fit your needs?
This is exactly what I had in mind.
I pushed a patch providing support
Hello Jose,
On Wed, Feb 10, 2010 at 4:34 AM, wrote:
>
--- snip -
>
> We could add two more callbacks to the pdf_fsys_impl_s structure to
> initialize and cleanup some private data of the filesystem
> implementation:
>
--- snip ---
>
> And then call those callbacks in the existing
Hi Scoot,
> Managing libcurl for the http filesystem and RIA will require
> pthreads, and the initialization and cleanup of some http-
> filesystem-wide resources (worker thread, libcurl resources).
> There are currently no filesystem init or cleanup routines
> defined (that I could find anyhow).
Hi Scott.
Managing libcurl for the http filesystem and RIA will require
pthreads, and the initialization and cleanup of some http-
filesystem-wide resources (worker thread, libcurl resources).
There are currently no filesystem init or cleanup routines
defined (that I could find any
Managing libcurl for the http filesystem and RIA will require
pthreads, and the initialization and cleanup of some http-
filesystem-wide resources (worker thread, libcurl resources).
There are currently no filesystem init or cleanup routines
defined (that I could find anyhow).
Is there any reason
Hi Scott.
The task says "using the 'pdf-fsys-html-' prefix." Should this
instead be " 'pdf-fsys-http-' prefix"?
Yes, it is 'pdf-fsys-http-' :)
Thanks for picking this task!
--
Jose E. Marchesijema...@gnu.org
GNU Project http://www.gnu.org
The task says "using the 'pdf-fsys-html-' prefix." Should this
instead be " 'pdf-fsys-http-' prefix"?
10 matches
Mail list logo
