[
https://issues.apache.org/jira/browse/SOLR-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898405#action_12898405
]
Robert Muir commented on SOLR-2034:
-----------------------------------
Hoss, thanks, I agree with regards to backwards compat, unfortunately its not
immediately obvious to me how to implement the versioning (seamless like you
said, would be preferable).
the only thing i see is the version in the response parser, but i will play
some and see if i can do it in a versioned way (any more pointers would be very
helpful).
ultimately the goal would be to make it easier for non-java clients to
implement this protocol. although the wiki says only the java client implements
this, i found an issue for the .NET client here:
http://code.google.com/p/solrnet/issues/detail?id=71
I took a look at the github source code
(http://github.com/mausch/SolrNet/blob/javabin/SolrNet/Impl/JavaBinCodec.cs)
and was a little concerned to see writeChars implemented with
Encoding.UTF8.GetBytes... I know its likely a work in progress etc, but I think
it illustrates the benefits of standard UTF-8.
> javabin should use UTF-8, not modified UTF-8
> --------------------------------------------
>
> Key: SOLR-2034
> URL: https://issues.apache.org/jira/browse/SOLR-2034
> Project: Solr
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: SOLR-2034.patch
>
>
> for better interoperability, javabin should use standard UTF-8 instead of
> modified UTF-8 (http://www.unicode.org/reports/tr26/)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
