Skip Menu |

This queue is for tickets about the Kafka CPAN distribution.

Report information
The Basics
Id: 97518
Status: rejected
Priority: 0/
Queue: Kafka
People
Owner: Nobody in particular
Requestors: MARKLE [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Jul 25 20:18:10 2014 MARKLE [...] cpan.org - Ticket created
Subject: no reason to restrict utf8 strings
YAML.pm LoadFile() creates utf8 strings by default, even if there are no utf8 characters in the YAML text file. The checks in Kafka::Connection etc. for utf8 characters end up making life difficult and tedious. There's no reason to restrict arguments to non-utf8 characters. utf8 characters can be allowed in internationalized host names, for instance. If it doesn't work, the user will figure it out. There is no reason to do excessive validation on the user's arguments to restrict the way they can use the library. Thank you. Mark
  Mon Aug 25 14:24:19 2014 SGLADKOV [...] cpan.org - Correspondence added
Kafka protocol is binary and does not support internal Perl unicode string representation. So, we either should disallow non-byte strings, like we do now, or silently encode them into binary representation. The latter approach works one-way only, so if user supplies some unicode string, and later gets it back from us, it will NOT have original encoding as Kafka server does not provide any way to store original encoding along with data. We prefer to let user handle encoding and decoding non-binary data instead of doing silent conversions with potential of data loss.
  Mon Aug 25 14:24:19 2014 The RT System itself - Status changed from 'new' to 'open'
  Mon Aug 25 14:24:20 2014 SGLADKOV [...] cpan.org - Status changed from 'open' to 'rejected'