You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Thomas Salemy <tp...@lehigh.edu> on 2018/09/14 02:18:11 UTC

[users@httpd] Developing Private Cache Module

Hello all,

I am a researcher at Lehigh University working on Transactional Memory, a
concurrency mechanism that radically simplifies parallel programming and
hopefully one day will improve the performance of many enterprise
applications.

I want to redevelop the shared object cache that is used to filter HTTP
requests. Specifically, I want to serve requests even faster by replacing
the module's current structure with this concurrency mechanism. In fact, I
have been working on this for a while but have not been able to figure out
how to properly redesign the module to incorporate the new concurrency
platform and have it work more than 80% of the time.

I am hoping that one of you might be able to describe to me more in detail
how this module works and the details of the current concurrency mechanism
supporting it so that I may redesign it and prove the value of
transactional memory in my research project.

Thanks!

––
Sincerely,
Thomas Salemy

Re: [users@httpd] Developing Private Cache Module

Posted by Luca Toscano <to...@gmail.com>.
Il giorno ven 14 set 2018 alle ore 06:39 Yann Ylavic
<yl...@gmail.com> ha scritto:
>
> Hi Thomas,
>
> On Fri, Sep 14, 2018 at 4:18 AM Thomas Salemy <tp...@lehigh.edu> wrote:
> >
> > I want to redevelop the shared object cache that is used to filter
> > HTTP requests. Specifically, I want to serve requests even faster by
> > replacing the module's current structure with this concurrency
> > mechanism.
>
> Could you please be more explicit on what "module" you are talking
> about, which source file/code?
>
> >
> > I am hoping that one of you might be able to describe to me more in
> > detail how this module works and the details of the current
> > concurrency mechanism supporting it so that I may redesign it and
> > prove the value of transactional memory in my research project.
>
> Looks interesting, but for now a bit too vague...
> Also, I think this discussion about design/code/implementation would
> better fit the dev@httpd.apache.org mailing list, for a wider
> developpers/technical audience.
>
> Thanks for reaching out to us anyway!

Other than what Yann mentioned, I'd suggest to read these documents to
have an idea about httpd modules and filters architecture (if you
haven't already done so):

https://httpd.apache.org/docs/2.4/developer/
https://httpd.apache.org/docs/2.4/developer/modguide.html
https://httpd.apache.org/docs/2.4/developer/output-filters.html
(and others)

Hope that helps!

Luca

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Re: [users@httpd] Developing Private Cache Module

Posted by Yann Ylavic <yl...@gmail.com>.
Hi Thomas,

On Fri, Sep 14, 2018 at 4:18 AM Thomas Salemy <tp...@lehigh.edu> wrote:
>
> I want to redevelop the shared object cache that is used to filter
> HTTP requests. Specifically, I want to serve requests even faster by
> replacing the module's current structure with this concurrency
> mechanism.

Could you please be more explicit on what "module" you are talking
about, which source file/code?

>
> I am hoping that one of you might be able to describe to me more in
> detail how this module works and the details of the current
> concurrency mechanism supporting it so that I may redesign it and
> prove the value of transactional memory in my research project.

Looks interesting, but for now a bit too vague...
Also, I think this discussion about design/code/implementation would
better fit the dev@httpd.apache.org mailing list, for a wider
developpers/technical audience.

Thanks for reaching out to us anyway!

Regards,
Yann.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org