[
https://issues.apache.org/jira/browse/WOOKIE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091061#comment-13091061
]
Paul Sharples edited comment on WOOKIE-206 at 8/25/11 3:11 PM:
---------------------------------------------------------------
Recreated problem as described and it works for me.
was (Author: psharples):
Recreated problem as described and it work for me.
> SharedDataKey not kept unique internally
> ----------------------------------------
>
> Key: WOOKIE-206
> URL: https://issues.apache.org/jira/browse/WOOKIE-206
> Project: Wookie
> Issue Type: Bug
> Affects Versions: 0.9.0
> Reporter: Scott Wilson
> Assignee: Scott Wilson
> Priority: Blocker
> Fix For: 0.9.1
>
>
> In earlier versions of Wookie, we had an "external" shared data key and an
> "internal" shared data key. The internal version was a hash of the external
> key + API key + Widget URI. This was to prevent collisions between contexts
> used in multiple sites.
> However, this seems to have disappeared at some point and now the
> sharedDataKey is simply persisted as-is. This means that, if you have
> multiple Wookie-enabled sites which reuse simple shared data keys (e.g. "1")
> then the widgets will use the same shared data.
> To recreate this problem, configure Wookie with two API keys. Instantiate a
> chat widget with the same Shared Data Key (e.g. "1") but a different API key.
> Note that the chat is synchronized across both widgets
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
