trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Kalidindi at" <>
Subject Re: Documentation / SDK correction
Date Mon, 26 Apr 2010 14:19:17 GMT
@Leif - My bad should have been more clear with my query.  Re-phrasing my

The current functionality of the cache is quiet awesome. Most of our needs
are being taken care of. Thank you guys for open sourcing the traffic

because the object store is quiet fast we are planning to use it as our
image server. We want to write a plugin which accepts an image, do certain
modifications etc to the plugin and then store it in the cache. Although it
is quiet clear you can do this easily by reading the current documentation
and the state-machine diagram (regarding where to hook your image processing
c code.) The aspect which we are having trouble is what is the best way to
handle the cache store from the plugins. Regarding that we couldn't find
proper documentation (i guess one of you is in the process of writing).

Chance is that we have missed the docs which discussed how to deal with
cache store from plugins in which case i apologize but please point me to
appropriate files.

Else one of you guys can help us out and once we are done with the plugin we
will document it and will look to contribute to the documentation of cache


On Mon, Apr 26, 2010 at 7:31 PM, Leif Hedstrom <> wrote:

> On 04/26/2010 04:10 AM, Sandeep Kalidindi at wrote:
>> shirish and i work at the same place.
>> we are planning to use traffic server in production. Need to write couple
>> of cache plugins very soon.
> Out of curiosity, what in the existing cache doesn't fit your needs? We are
> aware of a few shortcomings, but I'm sure John and the entire dev team would
> love to hear what else needs to be fixed, improved or added to the cache to
> suit more users.
> Also, why do you think you need two cache plugins? Are these two different
> apps? Note that you can only use one cache (and hence, one cache plugin) at
> a time, there is currently no way to "chain" or "selectively use" multiple
> cache implementations.
> Cheers,
> -- Leif

View raw message