> Brian Akins wrote:
> Some functions a provider should provide:
> init(args...) - initialize an instance :)
> open(instance, key) - open a cache object
> read_buffer(object, buffer, copy) - read entire object into buffer.
> buffer may be read only (ie, it may be mmapped or part of sql statement)
>
> Plüm, Rüdiger, wrote:
>
> I have been spending some time to remove the libcurl dependency by
> creating fake connection and requests. I didn't know we already have
> such functionality in proxy. Can you tell me where is that code to
> create fake connections/requests. I can use that code instea
Plüm, Rüdiger, wrote:
> I guess one of the reasons why mod_cache_requestor did not take off was its
> dependency on an external http client library. So what about creating
> a http client library and adding it to apr-util / creating apr-http-client
> as a SoC project?
>
> The httpd proxy code woul
> An example I'd like to do (or mentor someone) is a mod_memcached that
> could serve as the basis of memcached based modules. It could handle
> all the configuration details, errors, and general heavy lifting of
> memcached. It would then be very easy to write other modules that had
> hooks into
> - mod_cache_requestor (which i don't think really took off)
> and 2 active comitters.
I still haven't given up on it. :-) I am trying to remove the libcurl
dependency by creating mocked up connection and request. hopefully, it
would take off one day :-)
Hi,
As of now, we can not make requests without having actual
connection(conn_rec) to the server.
For example, mod-cache-requester needs to make request for popular and
soon-to-expire from cache pages so that these pages are reloaded in
the cache. right now, it has to rely on libcurl to re-reque
Hi,
My svn account is created now, and I have commited mod-cache-requester files.
http://svn.apache.org/repos/asf/httpd/mod_cache_requester/
Along with these files, I had to make some changes in mod_cache.c,
mod_cache.h and config.m4 as well. I am attaching patches for all
three files with this m
We tried to solve thundering herd problem wih cache-requester module
which I have not committed yet. It is currently available on source
forge.
I have not found enough time to work on it after summer of code was
over as I was busy with my thesis, internship. now I have just
relocated to calif rece
Hi All,
I would like to share some of my experiences (in brief :-) ) about
Summer of Code program.
I worked on mod-cache-requester as a part of this program. and I had
great time while working on this module; learned a lot, got a chance
to interact with great guys; worked on one of the most popul
On 8/24/05, Colm MacCarthaigh <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 24, 2005 at 09:18:54AM -0500, Parin Shah wrote:
> > > > I have fixed that memory leak problem. also added script to include
> > > > libcurl whenever this module is included.
> > >
>
> > I have fixed that memory leak problem. also added script to include
> > libcurl whenever this module is included.
>
> I hope that it doesn't mean that libcurl is going to be a permanent
> solution, when subrequests (with minor changes) could serve the same
> purpose.
Certainly not, We would h
Hi,
I have fixed that memory leak problem. also added script to include
libcurl whenever this module is included.
http://utdallas.edu/~parinshah/mod-c-requester.0.3.tar.gz
Thanks,
Parin.
On 8/23/05, Parin Shah <[EMAIL PROTECTED]> wrote:
> > > ohh, I thought I was taking car
> > ohh, I thought I was taking care of it. I mean, code frees the memory
> > when no longer needed except during the shutdown of server. anyway I
> > will go through the code again to check that. Also feel free to point
> > out the code which is causing memory leak problem.
>
> I'll look through
> > ohh, I thought I was taking care of it. I mean, code frees the memory
> > when no longer needed except during the shutdown of server. anyway I
> > will go through the code again to check that. Also feel free to point
> > out the code which is causing memory leak problem.
>
> I'll look through
>
> Cool. Very good start. Leaks memory like a sieve, but good start.
>
ohh, I thought I was taking care of it. I mean, code frees the memory
when no longer needed except during the shutdown of server. anyway I
will go through the code again to check that. Also feel free to point
out the code wh
> >
> > Content definitely should not be served from the cache after it has
> > expired imo. However I think an approach like;
> >
> > if((now + interval) > expired) {
> > if(!stat(tmpfile)) {
> > update_cache_from_backend();
> > }
> > }
> >
> > ie "revalidate the ca
, Parin Shah <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> please find initial version of mod-cache-requester at the following url.
>
> http://utdallas.edu/~parinshah/mod-c-requester.0.2.tar.gz
>
> As we have discussed the issue before, it is not possible (or atleast
> not pos
Hi All,
please find initial version of mod-cache-requester at the following url.
http://utdallas.edu/~parinshah/mod-c-requester.0.2.tar.gz
As we have discussed the issue before, it is not possible (or atleast
not possible w/o some refactoring) to use make-sub-request to
re-request all soon-to-e
> What I meant was that you modify the ap_read_request() to not crash when
> NULL is passed to it.
> As far as I am aware, the request_req only needs certain fields copied
> out of connection_req, not all of which are required.
>
- I played with it to make it work without conn_rec, but it doesnt
> Would there be value in teaching ap_read_request() how to not break if
> you called ap_read_request(NULL)?
>
Well, I couldnt find a way to do this. and with NULL value it crashes.
> Alternatively ap_read_request() could be broken up into
> ap_read_request() and ap_create_request(), which would
use the connection of
any current request_rec for that.
It would be really helpful if you can suggest me some pointers for this.
Thanks,
Parin.
On 8/8/05, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote:
> At 05:15 AM 8/8/2005, Graham Leggett wrote:
> >Parin Shah said:
> >
Hi All,
I am currently working on mod-cache-requester. This module stores
uri's of all the pages those are served from cache. and it re-request
all popular pages those are soon-to-expire from cache so that such
pages are not removed from the cache.
To implement that, mod-cache-requester should be
Hi again.
Rici help me out on this issue.
Thanks,
Parin.
On 7/24/05, Parin Shah <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> I am currently working on my first module, mod-cache-requester. I am
> planning to make it a sub-module of mod-cache.
>
> I have written a small pi
Hi All,
I am currently working on my first module, mod-cache-requester. I am
planning to make it a sub-module of mod-cache.
I have written a small piece of code which I want to integrate it with
mod-cache the way mod-mem-cache is integrated. i.e. it should have a
seperate .so file in the modules
ookup for what's expiring, just sleep
> until something needs to be regenerated.
> Bye
>
> Sergio
>
> -Original Message-
> From: Parin Shah [mailto:[EMAIL PROTECTED]
> Sent: venerdì 22 luglio 2005 8.02
> To: dev@httpd.apache.org
> Subject: Re: m
place.
Thanks,
Parin.
On 7/20/05, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Parin Shah wrote:
>
> > 2. how mod-cache-requester can generate the sub request just to reload
> > the content in the cache.
>
> Look inside mod_include - it uses subrequests to be able
d wait for next legitimate request.
Your thoughts on any/all on these issues would be really helpful.
Thanks
Parin.
On 7/19/05, Ian Holsman <[EMAIL PROTECTED]> wrote:
> Parin Shah wrote:
> >>you should be using a mix of
> >>
> >># requests
>
> you should be using a mix of
>
> # requests
> last access time
> cost of reproducing the request.
>
Just to double check, we would insert entry into the 'refresh queue'
only if the page is requested and the page is soon-to-be-expired. once
it is in the queue we would use above parameters to ca
On 7/16/05, Graham Leggett <[EMAIL PROTECTED]> wrote:
> Parin Shah wrote:
>
> > - I would prefer the approach where we maintain priority queue to keep
> > track of popularity. But again you guys have more insight and
> > understanding. so whichever approach you guys
On 7/15/05, Colm MacCarthaigh <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 15, 2005 at 01:23:29AM -0500, Parin Shah wrote:
> > - we need to maintain a counter for url in this case which would
> > decide the priority of the url. But mainting this counter should be a
> >
Thanks all for for your thoughts on this issue.
> > The priority re-fetch would make sure the
> > popular pages are always in cache, while others are allowed to die at
> > their expense.
>
>
> So every request for an object would update a counter for that url?
>
- we need to maintain a counter
> We have been down this road. The way one might solve it is to allow
> mod_cache to be able to reload an object while serving the "old" one.
>
> Example:
>
> cache /A for 600 seconds
>
> after 500 seconds, request /A with special header (or from special client,
> etc) and cache does not serve
> I believe the basic idea of
forwarding multiple requests on the back end can be a very good idea,
but needs some bounds as Graham suggests.> ..
its an interesting thought. But after Graham's opinion, I am not too
sure about performance improvement/overload incured by threads ratio.
if we could ga
> - Cache freshness of an URL is checked on each hit to the URL. This runs> the risk of allowing non-popular (but possibly expensive) URLs to expire
> without the chance to be refreshed.>
> - Cache freshness is checked in an independant thread, which monitors the> cached URLs for freshness at pred
Hi All,
I am a newbie. I am going to work on mod-cache and a new module
mod-cache-requester as a part of Soc program.
Small description of the module is as follows.
When the page expires from the cache, it is removed from cache and
thus next request has to wait until that page is reloaded by the
35 matches
Mail list logo
