[jira] [Created] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

Mikko Multanen created VYSPER-342: - Summary: Access to UTF-8 encoding and decoding is not thread safe Key: VYSPER-342 URL: https://issues.apache.org/jira/browse/VYSPER-342 Project: VYSPER

[jira] [Updated] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikko Multanen updated VYSPER-342: -- Attachment: fix_charset_util.patch Patch to fix CharsetUtil thread safety

Re: Codecs and CumulativeByteBuffer

Hi Emmanuel, Thanks for your comments! I imagine that slice() method would have a behaviour similar to the one of ByteBuffer. As in ByteBuffer, position based values (position, limit and mark) of the slice would be independent copies of the original IoBuffer ones, but the buffer content itself

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685471#comment-13685471 ] Bernd Fondermann commented on VYSPER-342: - thanks for the issue + contribution is

Re: Codecs and CumulativeByteBuffer

Le 6/17/13 1:32 PM, Raphaël Barazzutti a écrit : Hi Emmanuel, Thanks for your comments! I imagine that slice() method would have a behaviour similar to the one of ByteBuffer. As in ByteBuffer, position based values (position, limit and mark) of the slice would be independent copies of the

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685473#comment-13685473 ] Emmanuel Lecharny commented on VYSPER-342: -- I'm pretty sure that Mikko used

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685482#comment-13685482 ] Mikko Multanen commented on VYSPER-342: --- Emmanuel is right. I used thread locals to

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685484#comment-13685484 ] Bernd Fondermann commented on VYSPER-342: - is it? ok, what about my Commit:

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685486#comment-13685486 ] Bernd Fondermann commented on VYSPER-342: - what kind of performance issues? at

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685488#comment-13685488 ] Emmanuel Lecharny commented on VYSPER-342: -- When you have a synchronized block,

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685499#comment-13685499 ] Mikko Multanen commented on VYSPER-342: --- CharsetDecoder and CharsetEncoder are not

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685504#comment-13685504 ] Bernd Fondermann commented on VYSPER-342: - yep, I roughly know what synchronized

[jira] [Commented] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685508#comment-13685508 ] Bernd Fondermann commented on VYSPER-342: - @Mikko: ok, got it now. I'm reinstating

[jira] [Resolved] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann resolved VYSPER-342. - Resolution: Fixed Fix Version/s: 0.8 patch applied. thanks for contributing!

Re: Codecs and CumulativeByteBuffer

Le 6/17/13 1:47 PM, Emmanuel Lécharny a écrit : Le 6/17/13 1:32 PM, Raphaël Barazzutti a écrit : Hi Emmanuel, Thanks for your comments! I imagine that slice() method would have a behaviour similar to the one of ByteBuffer. As in ByteBuffer, position based values (position, limit and mark)

[jira] [Assigned] (VYSPER-342) Access to UTF-8 encoding and decoding is not thread safe

[ https://issues.apache.org/jira/browse/VYSPER-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bernd Fondermann reassigned VYSPER-342: --- Assignee: Bernd Fondermann Access to UTF-8 encoding and decoding is not thread

Re: Codecs and CumulativeByteBuffer

Hi Emmanuel, Thanks for your helpful comments, I think that I've now a better picture of how you expect things to work with IoBuffer. For sure IoBuffer is per session and not shared. But more specifically, I see that a the context should be an object pointing to IoBuffer and not an IoBuffer