You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficserver.apache.org by Nick Kew <ni...@apache.org> on 2013/09/17 13:04:33 UTC

Extending the API (Re: Could InkHashTable be leveraged by plugins?)

On 17 Sep 2013, at 10:09, Ethan Lai wrote:

> Hi,
> 
> I'm going to write a plugin, which needs to store some meta data in memory.
> Would like to know are there any ways to use InkHashTable data structure in my implementation? 

Using the plugin API, nope.  No such useful tools exposed.

At your own risk, yes of course you can #include the header and use the lib.

Which begs a question I'd like to ask: is there any good reason now not to
expose a lot more header files and a much richer API?  So the answer to
this question would be an obvious yes (and a plugin developer wouldn't
have to ask)!

Crossposting to dev@ where at least my question belongs.

-- 
Nick Kew


Re: Extending the API (Re: Could InkHashTable be leveraged by plugins?)

Posted by James Peach <jp...@apache.org>.
On Sep 17, 2013, at 4:04 AM, Nick Kew <ni...@apache.org> wrote:

> 
> On 17 Sep 2013, at 10:09, Ethan Lai wrote:
> 
>> Hi,
>> 
>> I'm going to write a plugin, which needs to store some meta data in memory.
>> Would like to know are there any ways to use InkHashTable data structure in my implementation? 
> 
> Using the plugin API, nope.  No such useful tools exposed.
> 
> At your own risk, yes of course you can #include the header and use the lib.
> 
> Which begs a question I'd like to ask: is there any good reason now not to
> expose a lot more header files and a much richer API?  So the answer to
> this question would be an obvious yes (and a plugin developer wouldn't
> have to ask)!

I'm generally against exposing "platform" functionality in the TSAPI. There's a zillion hash table implementations out there; it should be pretty easy to pull an appropriate one into your plugin.

J

Re: Extending the API (Re: Could InkHashTable be leveraged by plugins?)

Posted by James Peach <jp...@apache.org>.
On Sep 17, 2013, at 4:04 AM, Nick Kew <ni...@apache.org> wrote:

> 
> On 17 Sep 2013, at 10:09, Ethan Lai wrote:
> 
>> Hi,
>> 
>> I'm going to write a plugin, which needs to store some meta data in memory.
>> Would like to know are there any ways to use InkHashTable data structure in my implementation? 
> 
> Using the plugin API, nope.  No such useful tools exposed.
> 
> At your own risk, yes of course you can #include the header and use the lib.
> 
> Which begs a question I'd like to ask: is there any good reason now not to
> expose a lot more header files and a much richer API?  So the answer to
> this question would be an obvious yes (and a plugin developer wouldn't
> have to ask)!

I'm generally against exposing "platform" functionality in the TSAPI. There's a zillion hash table implementations out there; it should be pretty easy to pull an appropriate one into your plugin.

J