You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Theo Schlossnagle (JIRA)" <ji...@apache.org> on 2010/11/04 05:31:43 UTC

[jira] Commented: (TS-503) Add plugin APIs to allow for Session "private" data

    [ https://issues.apache.org/jira/browse/TS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928118#action_12928118 ] 

Theo Schlossnagle commented on TS-503:
--------------------------------------

Ideally, from the plugin perspective, you only need to be able to create one piece of plugin-local data for a "session" or a "transaction"...  If this is the case, then the int64id could instead be the void * that is the address of the plugin info.

Currently there is no way to get the plugin structure via the API... One way to do it in the modules is to make:

INKPluginRegistrationInfo info; (in init) static to the file and use &info as the key. 

> Add plugin APIs to allow for Session "private" data
> ---------------------------------------------------
>
>                 Key: TS-503
>                 URL: https://issues.apache.org/jira/browse/TS-503
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: InkAPI
>            Reporter: Leif Hedstrom
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Today, a plugin can store (and fetch) an opaque piece of data for the continuation, which is useful to preserve state between HOOKS. There is also a similar API for transaction data. However, as far as I can tell, there's no way to have per session private data. It'd be useful to add the equivalent here, e.g. something like
>     INKReturnCode INKSsnDataSet(INKHttpSsn ssn, int64 id, void* data);
>     void* INKSsnDataGet(NKHttpSsn ssn, int64 id);
> The id is a unique identifier, registered via a different API in the plugin. This ID allows for more than one plugin to set/get session data structure, without stepping over each other. IDs can either be randomly assigned, or reserved in a plugin ID "registry".

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.