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

[jira] Updated: (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:all-tabpanel ]

Leif Hedstrom updated TS-503:
-----------------------------

    Fix Version/s: 2.1.5

> 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
>             Fix For: 2.1.5
>
>   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.