On Tue, 03 Jul 2012 13:27:11 -0000, "the_a_rioch" <ariochthe@...>
wrote:

>> We could introduce this in Jaybird 2.3 as an optional default
> (requiring a
>> Java system property to enable it).
>
> That is a no-op.
> Why would anyone do it?
>
> Those who know and care are already fixing encoding in URL.
> Those who do not know - they would not know about that change too.
> Those who do not care... they do not care.

But it would give an opportunity to
1) Give people a chance to try it out and test things
2) Give additional time for people to be aware of the upcoming change

It is not wise to just change something which - for better or for worse -
has been a fundamental part of Jaybird for over 12 years without large
problems. You are probably the first to complain about the default
connection characterset and create such a big fuss about it. Yes it is
annoying, and can cause problems, but as I said before: changing this can
(and probably will) break things for others.

>> Jaybird 3.0 we switch this around:
>
> Magic of ".0" numbers...
>
> It took 4 years to shift from 2.1.6 to 2.2.0 and don't know how many to
> move 2.1.0 to 2.2.0
>
> You are not Mozilla, incrementing version each x months.
> I do not expect even 2.3 anytime soon.
> And 3.0 sounds like postponing to forever.

As I said before I don't like the way your e-mail contains dismissive and
disparaging responses like above. Let me explain this: this is not the
immaterial compensation I am looking for when doing volunteer work. I work
on Jaybird in my free time, when and if my schedule allows it (and my
social life will always come first!) without any compensation. I am even
replying to e-mail on this list from my normal daytime job, which also
means I have to stay at work longer to compensate that time. It is not as
if I work for a company which pays me to work on the driver full-time, or
that I am being paid to get snubbed by 'customers'.

Mark