You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by Leif Hedstrom <zw...@apache.org> on 2015/04/24 16:09:08 UTC
[v6.0.0] Experimental Plugins -> Stable
Hi all,
Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
Please discuss and suggest which of these should be promoted to stable.
— Leif
ats_pagespeed/
authproxy/
background_fetch/
balancer/
buffer_upload/
cache_promote/
channel_stats/
collapsed_connection/
custom_redirect/
epic/
escalate/
esi/
generator/
geoip_acl/
header_normalize/
healthchecks/
hipes/
Makefile.am
Makefile.in
memcached_remap/
metalink/
mysql_remap/
regex_revalidate/
remap_stats/
s3_auth/
spdy/
ssl_cert_loader/
sslheaders/
stale_while_revalidate/
ts_lua/
url_sig/
xdebug/
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Miles Libbey <ml...@apache.org>.
I'm not sure I'd believe a plugin was ready to be moved out of experimental if it doesn't have a documentation page (eg, other than a README in the code directory, though the doc page wouldn't have to have different content).miles
On Wednesday, April 29, 2015 9:15 PM, Steven Hunter <st...@gmail.com> wrote:
Stable_connection/StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
>
> ats_pagespeed/
> authproxy/
> background_fetch/
> balancer/
> buffer_upload/
> cache_promote/
> channel_stats/
> stable_connection/
> custom_redirect/
> epic/
> escalate/
> esi/
> generator/
> geoip_acl/
> header_normalize/
> healthchecks/
> hipes/
> Makefile.am
> Makefile.in
> memcached_remap/
> metalink/
> mysql_remap/
> regex_revalidate/
> remap_stats/
> s3_auth/
> spdy/
> ssl_cert_loader/
> sslheaders/
> stale_while_revalidate/
> ts_lua/
> url_sig/
> xdebug/
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Miles Libbey <ml...@apache.org>.
I'm not sure I'd believe a plugin was ready to be moved out of experimental if it doesn't have a documentation page (eg, other than a README in the code directory, though the doc page wouldn't have to have different content).miles
On Wednesday, April 29, 2015 9:15 PM, Steven Hunter <st...@gmail.com> wrote:
Stable_connection/StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
>
> ats_pagespeed/
> authproxy/
> background_fetch/
> balancer/
> buffer_upload/
> cache_promote/
> channel_stats/
> stable_connection/
> custom_redirect/
> epic/
> escalate/
> esi/
> generator/
> geoip_acl/
> header_normalize/
> healthchecks/
> hipes/
> Makefile.am
> Makefile.in
> memcached_remap/
> metalink/
> mysql_remap/
> regex_revalidate/
> remap_stats/
> s3_auth/
> spdy/
> ssl_cert_loader/
> sslheaders/
> stale_while_revalidate/
> ts_lua/
> url_sig/
> xdebug/
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Steven Hunter <st...@gmail.com>.
Stable_connection/
StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide
which, if any, of these should be moved to a stable state. Once stable,
incompatible changes within a major release would not be accepted. Being
stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
>
> ats_pagespeed/
> authproxy/
> background_fetch/
> balancer/
> buffer_upload/
> cache_promote/
> channel_stats/
> stable_connection/
> custom_redirect/
> epic/
> escalate/
> esi/
> generator/
> geoip_acl/
> header_normalize/
> healthchecks/
> hipes/
> Makefile.am
> Makefile.in
> memcached_remap/
> metalink/
> mysql_remap/
> regex_revalidate/
> remap_stats/
> s3_auth/
> spdy/
> ssl_cert_loader/
> sslheaders/
> stale_while_revalidate/
> ts_lua/
> url_sig/
> xdebug/
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 11:03 AM, Bryan Call <bc...@apache.org> wrote:
>
> When do you think you will be open sourcing the plugin?
Hopefully for 6.0.0. We’ve worked with the IETF WG to get some things changed, and will continue to do so. I’d also encourage everyone who’s got use cases for URL signing to participate in this WG discussion.
Cheers,
— leif
>
> -Bryan
>
>
>
>
>> On Apr 24, 2015, at 7:48 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>
>>
>>> On Apr 24, 2015, at 8:37 AM, Phil Sorber <sorber@apache.org <ma...@apache.org>> wrote:
>>>
>>> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>
>>>>
>>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Below is a list of currently “experimental” plugins. We should decide
>>>> which, if any, of these should be moved to a stable state. Once stable,
>>>> incompatible changes within a major release would not be accepted. Being
>>>> stable also means that we expect it to be fully maintained and supported.
>>>>>
>>>>> Please discuss and suggest which of these should be promoted to stable.
>>>>>
>>>>> — Leif
>>>>
>>>> These are the two I personally think we should seriously consider
>>>> promoting. I use them daily, and I think they are generally used and useful
>>>> as well:
>>>>
>>>>>
>>>>> authproxy/
>>>>> background_fetch/
>>>>
>>>>
>>>>
>>>> — Leif
>>>>
>>>>
>>> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
>>
>>
>> I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
>>
>> That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
>>
>> The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03 <https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03>.
>>
>> Cheers,
>>
>> — Leif
>>
>>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 11:03 AM, Bryan Call <bc...@apache.org> wrote:
>
> When do you think you will be open sourcing the plugin?
Hopefully for 6.0.0. We’ve worked with the IETF WG to get some things changed, and will continue to do so. I’d also encourage everyone who’s got use cases for URL signing to participate in this WG discussion.
Cheers,
— leif
>
> -Bryan
>
>
>
>
>> On Apr 24, 2015, at 7:48 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>
>>
>>> On Apr 24, 2015, at 8:37 AM, Phil Sorber <sorber@apache.org <ma...@apache.org>> wrote:
>>>
>>> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>
>>>>
>>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Below is a list of currently “experimental” plugins. We should decide
>>>> which, if any, of these should be moved to a stable state. Once stable,
>>>> incompatible changes within a major release would not be accepted. Being
>>>> stable also means that we expect it to be fully maintained and supported.
>>>>>
>>>>> Please discuss and suggest which of these should be promoted to stable.
>>>>>
>>>>> — Leif
>>>>
>>>> These are the two I personally think we should seriously consider
>>>> promoting. I use them daily, and I think they are generally used and useful
>>>> as well:
>>>>
>>>>>
>>>>> authproxy/
>>>>> background_fetch/
>>>>
>>>>
>>>>
>>>> — Leif
>>>>
>>>>
>>> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
>>
>>
>> I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
>>
>> That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
>>
>> The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03 <https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03>.
>>
>> Cheers,
>>
>> — Leif
>>
>>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Bryan Call <bc...@apache.org>.
When do you think you will be open sourcing the plugin?
-Bryan
> On Apr 24, 2015, at 7:48 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
>> On Apr 24, 2015, at 8:37 AM, Phil Sorber <sorber@apache.org <ma...@apache.org>> wrote:
>>
>> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>
>>>
>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Below is a list of currently “experimental” plugins. We should decide
>>> which, if any, of these should be moved to a stable state. Once stable,
>>> incompatible changes within a major release would not be accepted. Being
>>> stable also means that we expect it to be fully maintained and supported.
>>>>
>>>> Please discuss and suggest which of these should be promoted to stable.
>>>>
>>>> — Leif
>>>
>>> These are the two I personally think we should seriously consider
>>> promoting. I use them daily, and I think they are generally used and useful
>>> as well:
>>>
>>>>
>>>> authproxy/
>>>> background_fetch/
>>>
>>>
>>>
>>> — Leif
>>>
>>>
>> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
>
>
> I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
>
> That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
>
> The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03 <https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03>.
>
> Cheers,
>
> — Leif
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Bryan Call <bc...@apache.org>.
When do you think you will be open sourcing the plugin?
-Bryan
> On Apr 24, 2015, at 7:48 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>
>
>> On Apr 24, 2015, at 8:37 AM, Phil Sorber <sorber@apache.org <ma...@apache.org>> wrote:
>>
>> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>
>>>
>>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zwoop@apache.org <ma...@apache.org>> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> Below is a list of currently “experimental” plugins. We should decide
>>> which, if any, of these should be moved to a stable state. Once stable,
>>> incompatible changes within a major release would not be accepted. Being
>>> stable also means that we expect it to be fully maintained and supported.
>>>>
>>>> Please discuss and suggest which of these should be promoted to stable.
>>>>
>>>> — Leif
>>>
>>> These are the two I personally think we should seriously consider
>>> promoting. I use them daily, and I think they are generally used and useful
>>> as well:
>>>
>>>>
>>>> authproxy/
>>>> background_fetch/
>>>
>>>
>>>
>>> — Leif
>>>
>>>
>> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
>
>
> I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
>
> That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
>
> The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03 <https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03>.
>
> Cheers,
>
> — Leif
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 8:37 AM, Phil Sorber <so...@apache.org> wrote:
>
> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zw...@apache.org> wrote:
>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “experimental” plugins. We should decide
>> which, if any, of these should be moved to a stable state. Once stable,
>> incompatible changes within a major release would not be accepted. Being
>> stable also means that we expect it to be fully maintained and supported.
>>>
>>> Please discuss and suggest which of these should be promoted to stable.
>>>
>>> — Leif
>>
>> These are the two I personally think we should seriously consider
>> promoting. I use them daily, and I think they are generally used and useful
>> as well:
>>
>>>
>>> authproxy/
>>> background_fetch/
>>
>>
>>
>> — Leif
>>
>>
> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03.
Cheers,
— Leif
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 8:37 AM, Phil Sorber <so...@apache.org> wrote:
>
> On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zw...@apache.org> wrote:
>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “experimental” plugins. We should decide
>> which, if any, of these should be moved to a stable state. Once stable,
>> incompatible changes within a major release would not be accepted. Being
>> stable also means that we expect it to be fully maintained and supported.
>>>
>>> Please discuss and suggest which of these should be promoted to stable.
>>>
>>> — Leif
>>
>> These are the two I personally think we should seriously consider
>> promoting. I use them daily, and I think they are generally used and useful
>> as well:
>>
>>>
>>> authproxy/
>>> background_fetch/
>>
>>
>>
>> — Leif
>>
>>
> I'd like to nominate regex_revalidate, remap_stats, and url_sig.
I’m a little bit on the edge with url_sig. We’re working on a plugin that implements the CDNI Signed URL spec, which I think is a nicer way to go forward. The specs from CDNI would not allow the “bit-field” features that url_sig has (yet at least). But I’d encourage people to look at the CDNI spec over e.g. url_sig or other custom made URL signing protocols.
That much said, I’m merely -0 on promoting url_sig to stable, i.e. I’d prefer to see it deprecated over time, but I don’t care strongly.
The CDNI specs are at https://tools.ietf.org/html/draft-ietf-cdni-uri-signing-03.
Cheers,
— Leif
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Phil Sorber <so...@apache.org>.
On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >
> > Hi all,
> >
> > Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >
> > Please discuss and suggest which of these should be promoted to stable.
> >
> > — Leif
>
> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
>
> >
> > authproxy/
> > background_fetch/
>
>
>
> — Leif
>
>
I'd like to nominate regex_revalidate, remap_stats, and url_sig.
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Phil Sorber <so...@apache.org>.
On Fri, Apr 24, 2015 at 8:18 AM Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >
> > Hi all,
> >
> > Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >
> > Please discuss and suggest which of these should be promoted to stable.
> >
> > — Leif
>
> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
>
> >
> > authproxy/
> > background_fetch/
>
>
>
> — Leif
>
>
I'd like to nominate regex_revalidate, remap_stats, and url_sig.
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Randeep <ra...@gmail.com>.
Hi,
+1 for background_fetch. I have tested it and its working fine. It is very
useful when the user request for large media files.
Regards,
Randeep
On Mon, Apr 27, 2015 at 8:39 PM, Sudheer Vinukonda <su...@yahoo-inc.com>
wrote:
> We have been running the below *experimental* plugins in production, so, I
> am +1 on promoting these to stable (some of this have already received +1
> votes, but, I am listing them anyway, to possibly make the vote stronger ;)
> ):
>
> - regex_revalidate
> - background_fetch
> - buffer_upload
> - esi
>
> Thanks,
>
> Sudheer
>
> ------------------------------
> *From:* Shu Kit Chan <ch...@gmail.com>
> *To:* "dev@trafficserver.apache.org" <de...@trafficserver.apache.org>
> *Cc:* "users@trafficserver.apache.org" <us...@trafficserver.apache.org>
> *Sent:* Friday, April 24, 2015 12:56 PM
> *Subject:* Re: [v6.0.0] Experimental Plugins -> Stable
>
> That's true. Me and portl4t are still having plans for a few more
> substantial additions to the plugin in the upcoming weeks.
>
> I do want to try making it to the "stable" for 6.0.0. Will work on those
> additions soon and then shoot for sending an email out for a API review
> with hopefully substantial enough time before 6.0.0
>
> Another plugin I have is the ESI plugin. I think it is fairly stable, with
> at least some usage. I do have a patch soon for a improvement to use the
> streaming mode of the FetchSM. After that, there isn't other works planned
> from my side. Thoughts on making this to the "stable"?
>
> Thanks.
>
> Kit
>
>
>
>
> On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> >
> > > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> > jasonjwwilliams@gmail.com> wrote:
> > >
> > > I personally would like to see ts_lua go stable.
> >
> >
> > I think that’s up to Kit and the other people working on the plugin to
> > decide. I sort of feel that it’s still changing enough that making it
> > stable will make things much more difficult for them. But alas, I’m not a
> > developer on this project.
> >
> > What I do feel strongly about though is that *before* we make the Lua
> > plugin stable, we do a thorough API review of all the APIs that now would
> > become frozen. This is a lot of work though, but needs to be done, before
> > we commit to it being stable.
> >
> > Just my $.01,
> >
> > — leif
> >
> > >
> > >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> > >>
> > >>
> > >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> > >>>
> > >>> Hi all,
> > >>>
> > >>> Below is a list of currently “experimental” plugins. We should decide
> > which, if any, of these should be moved to a stable state. Once stable,
> > incompatible changes within a major release would not be accepted. Being
> > stable also means that we expect it to be fully maintained and supported.
> > >>>
> > >>> Please discuss and suggest which of these should be promoted to
> stable.
> > >>>
> > >>> — Leif
> > >>
> > >> These are the two I personally think we should seriously consider
> > promoting. I use them daily, and I think they are generally used and
> useful
> > as well:
> > >>
> > >>>
> > >>> authproxy/
> > >>> background_fetch/
> > >>
> > >>
> > >>
> > >> — Leif
> > >>
> >
> >
>
>
>
--
Randeep
Mob: +919447831699[kerala]
Mob: +919880050349[B'lore]
http://twitter.com/Randeeppr
http://in.linkedin.com/in/randeeppr
[image: --]
Randeep Raman
[image: http://]about.me/Randeeppr
<http://about.me/Randeeppr>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Randeep <ra...@gmail.com>.
Hi,
+1 for background_fetch. I have tested it and its working fine. It is very
useful when the user request for large media files.
Regards,
Randeep
On Mon, Apr 27, 2015 at 8:39 PM, Sudheer Vinukonda <su...@yahoo-inc.com>
wrote:
> We have been running the below *experimental* plugins in production, so, I
> am +1 on promoting these to stable (some of this have already received +1
> votes, but, I am listing them anyway, to possibly make the vote stronger ;)
> ):
>
> - regex_revalidate
> - background_fetch
> - buffer_upload
> - esi
>
> Thanks,
>
> Sudheer
>
> ------------------------------
> *From:* Shu Kit Chan <ch...@gmail.com>
> *To:* "dev@trafficserver.apache.org" <de...@trafficserver.apache.org>
> *Cc:* "users@trafficserver.apache.org" <us...@trafficserver.apache.org>
> *Sent:* Friday, April 24, 2015 12:56 PM
> *Subject:* Re: [v6.0.0] Experimental Plugins -> Stable
>
> That's true. Me and portl4t are still having plans for a few more
> substantial additions to the plugin in the upcoming weeks.
>
> I do want to try making it to the "stable" for 6.0.0. Will work on those
> additions soon and then shoot for sending an email out for a API review
> with hopefully substantial enough time before 6.0.0
>
> Another plugin I have is the ESI plugin. I think it is fairly stable, with
> at least some usage. I do have a patch soon for a improvement to use the
> streaming mode of the FetchSM. After that, there isn't other works planned
> from my side. Thoughts on making this to the "stable"?
>
> Thanks.
>
> Kit
>
>
>
>
> On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> >
> > > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> > jasonjwwilliams@gmail.com> wrote:
> > >
> > > I personally would like to see ts_lua go stable.
> >
> >
> > I think that’s up to Kit and the other people working on the plugin to
> > decide. I sort of feel that it’s still changing enough that making it
> > stable will make things much more difficult for them. But alas, I’m not a
> > developer on this project.
> >
> > What I do feel strongly about though is that *before* we make the Lua
> > plugin stable, we do a thorough API review of all the APIs that now would
> > become frozen. This is a lot of work though, but needs to be done, before
> > we commit to it being stable.
> >
> > Just my $.01,
> >
> > — leif
> >
> > >
> > >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> > >>
> > >>
> > >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> > >>>
> > >>> Hi all,
> > >>>
> > >>> Below is a list of currently “experimental” plugins. We should decide
> > which, if any, of these should be moved to a stable state. Once stable,
> > incompatible changes within a major release would not be accepted. Being
> > stable also means that we expect it to be fully maintained and supported.
> > >>>
> > >>> Please discuss and suggest which of these should be promoted to
> stable.
> > >>>
> > >>> — Leif
> > >>
> > >> These are the two I personally think we should seriously consider
> > promoting. I use them daily, and I think they are generally used and
> useful
> > as well:
> > >>
> > >>>
> > >>> authproxy/
> > >>> background_fetch/
> > >>
> > >>
> > >>
> > >> — Leif
> > >>
> >
> >
>
>
>
--
Randeep
Mob: +919447831699[kerala]
Mob: +919880050349[B'lore]
http://twitter.com/Randeeppr
http://in.linkedin.com/in/randeeppr
[image: --]
Randeep Raman
[image: http://]about.me/Randeeppr
<http://about.me/Randeeppr>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Sudheer Vinukonda <su...@yahoo-inc.com.INVALID>.
We have been running the below *experimental* plugins in production, so, I am +1 on promoting these to stable (some of this have already received +1 votes, but, I am listing them anyway, to possibly make the vote stronger ;) ):
- regex_revalidate- background_fetch- buffer_upload- esi
Thanks,
Sudheer
From: Shu Kit Chan <ch...@gmail.com>
To: "dev@trafficserver.apache.org" <de...@trafficserver.apache.org>
Cc: "users@trafficserver.apache.org" <us...@trafficserver.apache.org>
Sent: Friday, April 24, 2015 12:56 PM
Subject: Re: [v6.0.0] Experimental Plugins -> Stable
That's true. Me and portl4t are still having plans for a few more
substantial additions to the plugin in the upcoming weeks.
I do want to try making it to the "stable" for 6.0.0. Will work on those
additions soon and then shoot for sending an email out for a API review
with hopefully substantial enough time before 6.0.0
Another plugin I have is the ESI plugin. I think it is fairly stable, with
at least some usage. I do have a patch soon for a improvement to use the
streaming mode of the FetchSM. After that, there isn't other works planned
from my side. Thoughts on making this to the "stable"?
Thanks.
Kit
On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> jasonjwwilliams@gmail.com> wrote:
> >
> > I personally would like to see ts_lua go stable.
>
>
> I think that’s up to Kit and the other people working on the plugin to
> decide. I sort of feel that it’s still changing enough that making it
> stable will make things much more difficult for them. But alas, I’m not a
> developer on this project.
>
> What I do feel strongly about though is that *before* we make the Lua
> plugin stable, we do a thorough API review of all the APIs that now would
> become frozen. This is a lot of work though, but needs to be done, before
> we commit to it being stable.
>
> Just my $.01,
>
> — leif
>
> >
> >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >>>
> >>> Please discuss and suggest which of these should be promoted to stable.
> >>>
> >>> — Leif
> >>
> >> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
> >>
> >>>
> >>> authproxy/
> >>> background_fetch/
> >>
> >>
> >>
> >> — Leif
> >>
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Sudheer Vinukonda <su...@yahoo-inc.com>.
We have been running the below *experimental* plugins in production, so, I am +1 on promoting these to stable (some of this have already received +1 votes, but, I am listing them anyway, to possibly make the vote stronger ;) ):
- regex_revalidate- background_fetch- buffer_upload- esi
Thanks,
Sudheer
From: Shu Kit Chan <ch...@gmail.com>
To: "dev@trafficserver.apache.org" <de...@trafficserver.apache.org>
Cc: "users@trafficserver.apache.org" <us...@trafficserver.apache.org>
Sent: Friday, April 24, 2015 12:56 PM
Subject: Re: [v6.0.0] Experimental Plugins -> Stable
That's true. Me and portl4t are still having plans for a few more
substantial additions to the plugin in the upcoming weeks.
I do want to try making it to the "stable" for 6.0.0. Will work on those
additions soon and then shoot for sending an email out for a API review
with hopefully substantial enough time before 6.0.0
Another plugin I have is the ESI plugin. I think it is fairly stable, with
at least some usage. I do have a patch soon for a improvement to use the
streaming mode of the FetchSM. After that, there isn't other works planned
from my side. Thoughts on making this to the "stable"?
Thanks.
Kit
On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> jasonjwwilliams@gmail.com> wrote:
> >
> > I personally would like to see ts_lua go stable.
>
>
> I think that’s up to Kit and the other people working on the plugin to
> decide. I sort of feel that it’s still changing enough that making it
> stable will make things much more difficult for them. But alas, I’m not a
> developer on this project.
>
> What I do feel strongly about though is that *before* we make the Lua
> plugin stable, we do a thorough API review of all the APIs that now would
> become frozen. This is a lot of work though, but needs to be done, before
> we commit to it being stable.
>
> Just my $.01,
>
> — leif
>
> >
> >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >>>
> >>> Please discuss and suggest which of these should be promoted to stable.
> >>>
> >>> — Leif
> >>
> >> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
> >>
> >>>
> >>> authproxy/
> >>> background_fetch/
> >>
> >>
> >>
> >> — Leif
> >>
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Shu Kit Chan <ch...@gmail.com>.
That's true. Me and portl4t are still having plans for a few more
substantial additions to the plugin in the upcoming weeks.
I do want to try making it to the "stable" for 6.0.0. Will work on those
additions soon and then shoot for sending an email out for a API review
with hopefully substantial enough time before 6.0.0
Another plugin I have is the ESI plugin. I think it is fairly stable, with
at least some usage. I do have a patch soon for a improvement to use the
streaming mode of the FetchSM. After that, there isn't other works planned
from my side. Thoughts on making this to the "stable"?
Thanks.
Kit
On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> jasonjwwilliams@gmail.com> wrote:
> >
> > I personally would like to see ts_lua go stable.
>
>
> I think that’s up to Kit and the other people working on the plugin to
> decide. I sort of feel that it’s still changing enough that making it
> stable will make things much more difficult for them. But alas, I’m not a
> developer on this project.
>
> What I do feel strongly about though is that *before* we make the Lua
> plugin stable, we do a thorough API review of all the APIs that now would
> become frozen. This is a lot of work though, but needs to be done, before
> we commit to it being stable.
>
> Just my $.01,
>
> — leif
>
> >
> >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >>>
> >>> Please discuss and suggest which of these should be promoted to stable.
> >>>
> >>> — Leif
> >>
> >> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
> >>
> >>>
> >>> authproxy/
> >>> background_fetch/
> >>
> >>
> >>
> >> — Leif
> >>
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Shu Kit Chan <ch...@gmail.com>.
That's true. Me and portl4t are still having plans for a few more
substantial additions to the plugin in the upcoming weeks.
I do want to try making it to the "stable" for 6.0.0. Will work on those
additions soon and then shoot for sending an email out for a API review
with hopefully substantial enough time before 6.0.0
Another plugin I have is the ESI plugin. I think it is fairly stable, with
at least some usage. I do have a patch soon for a improvement to use the
streaming mode of the FetchSM. After that, there isn't other works planned
from my side. Thoughts on making this to the "stable"?
Thanks.
Kit
On Fri, Apr 24, 2015 at 12:37 PM, Leif Hedstrom <zw...@apache.org> wrote:
>
> > On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <
> jasonjwwilliams@gmail.com> wrote:
> >
> > I personally would like to see ts_lua go stable.
>
>
> I think that’s up to Kit and the other people working on the plugin to
> decide. I sort of feel that it’s still changing enough that making it
> stable will make things much more difficult for them. But alas, I’m not a
> developer on this project.
>
> What I do feel strongly about though is that *before* we make the Lua
> plugin stable, we do a thorough API review of all the APIs that now would
> become frozen. This is a lot of work though, but needs to be done, before
> we commit to it being stable.
>
> Just my $.01,
>
> — leif
>
> >
> >> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
> >>
> >>
> >>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> Below is a list of currently “experimental” plugins. We should decide
> which, if any, of these should be moved to a stable state. Once stable,
> incompatible changes within a major release would not be accepted. Being
> stable also means that we expect it to be fully maintained and supported.
> >>>
> >>> Please discuss and suggest which of these should be promoted to stable.
> >>>
> >>> — Leif
> >>
> >> These are the two I personally think we should seriously consider
> promoting. I use them daily, and I think they are generally used and useful
> as well:
> >>
> >>>
> >>> authproxy/
> >>> background_fetch/
> >>
> >>
> >>
> >> — Leif
> >>
>
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <ja...@gmail.com> wrote:
>
> I personally would like to see ts_lua go stable.
I think that’s up to Kit and the other people working on the plugin to decide. I sort of feel that it’s still changing enough that making it stable will make things much more difficult for them. But alas, I’m not a developer on this project.
What I do feel strongly about though is that *before* we make the Lua plugin stable, we do a thorough API review of all the APIs that now would become frozen. This is a lot of work though, but needs to be done, before we commit to it being stable.
Just my $.01,
— leif
>
>> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>>>
>>> Please discuss and suggest which of these should be promoted to stable.
>>>
>>> — Leif
>>
>> These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>>
>>>
>>> authproxy/
>>> background_fetch/
>>
>>
>>
>> — Leif
>>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 10:18 AM, Jason J. W. Williams <ja...@gmail.com> wrote:
>
> I personally would like to see ts_lua go stable.
I think that’s up to Kit and the other people working on the plugin to decide. I sort of feel that it’s still changing enough that making it stable will make things much more difficult for them. But alas, I’m not a developer on this project.
What I do feel strongly about though is that *before* we make the Lua plugin stable, we do a thorough API review of all the APIs that now would become frozen. This is a lot of work though, but needs to be done, before we commit to it being stable.
Just my $.01,
— leif
>
>> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
>>
>>
>>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>>
>>> Hi all,
>>>
>>> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>>>
>>> Please discuss and suggest which of these should be promoted to stable.
>>>
>>> — Leif
>>
>> These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>>
>>>
>>> authproxy/
>>> background_fetch/
>>
>>
>>
>> — Leif
>>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by "Jason J. W. Williams" <ja...@gmail.com>.
I personally would like to see ts_lua go stable.
> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
>
>
>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>> Hi all,
>>
>> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>>
>> Please discuss and suggest which of these should be promoted to stable.
>>
>> — Leif
>
> These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>
>>
>> authproxy/
>> background_fetch/
>
>
>
> — Leif
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by "Jason J. W. Williams" <ja...@gmail.com>.
I personally would like to see ts_lua go stable.
> On Apr 24, 2015, at 7:18, Leif Hedstrom <zw...@apache.org> wrote:
>
>
>> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>>
>> Hi all,
>>
>> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>>
>> Please discuss and suggest which of these should be promoted to stable.
>>
>> — Leif
>
> These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>
>>
>> authproxy/
>> background_fetch/
>
>
>
> — Leif
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>
> authproxy/
> background_fetch/
— Leif
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Leif Hedstrom <zw...@apache.org>.
> On Apr 24, 2015, at 8:09 AM, Leif Hedstrom <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide which, if any, of these should be moved to a stable state. Once stable, incompatible changes within a major release would not be accepted. Being stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
These are the two I personally think we should seriously consider promoting. I use them daily, and I think they are generally used and useful as well:
>
> authproxy/
> background_fetch/
— Leif
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Steven Hunter <st...@gmail.com>.
Stable_connection/
StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide
which, if any, of these should be moved to a stable state. Once stable,
incompatible changes within a major release would not be accepted. Being
stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
>
> ats_pagespeed/
> authproxy/
> background_fetch/
> balancer/
> buffer_upload/
> cache_promote/
> channel_stats/
> stable_connection/
> custom_redirect/
> epic/
> escalate/
> esi/
> generator/
> geoip_acl/
> header_normalize/
> healthchecks/
> hipes/
> Makefile.am
> Makefile.in
> memcached_remap/
> metalink/
> mysql_remap/
> regex_revalidate/
> remap_stats/
> s3_auth/
> spdy/
> ssl_cert_loader/
> sslheaders/
> stale_while_revalidate/
> ts_lua/
> url_sig/
> xdebug/
>
Re: [v6.0.0] Experimental Plugins -> Stable
Posted by Steven Hunter <st...@gmail.com>.
StevenHunter
On Apr 24, 2015 11:09 AM, "Leif Hedstrom" <zw...@apache.org> wrote:
>
> Hi all,
>
> Below is a list of currently “experimental” plugins. We should decide
which, if any, of these should be moved to a stable state. Once stable,
incompatible changes within a major release would not be accepted. Being
stable also means that we expect it to be fully maintained and supported.
>
> Please discuss and suggest which of these should be promoted to stable.
>
> — Leif
>
> ats_pagespeed_stable/
> authproxy/
> background_fetch/
> balancer/
> buffer_upload/
> cache_promote/
> channel_stats/
> collapsed_connection/
> custom_redirect/
> epic/
> escalate/
> esi/
> generator/
> geoip_acl/
> header_normalize/
> healthchecks/
> hipes/
> Makefile.am
> Makefile.in
> memcached_remap/
> metalink/
> mysql_remap/
> regex_revalidate/
> remap_stats/
> s3_auth/
> spdy/
> ssl_cert_loader/
> sslheaders/
> stale_while_revalidate/
> ts_lua/
> url_sig/
> xdebug/
>