On Thursday 17 June 2004 3:25 pm, Julian Missig wrote: > Protocols do not move forward by sheer will of the council. The > /reason/ those JEPs are /still/ experimental is because of lack of > implementation attempts.
Do we really want to relive the DTCP disaster again? Ever since that backlash, I'm afraid to implement anything that doesn't say Draft. > JEPs do not move forward by sheer will of Council or JEP authors. > Client-based JEPs need client implementations to test them and work out > bugs... and then the Council can start moving things forward based on > real experience. Has the Council opinion changed? If so, I wasn't aware of it. Real experience is apparently overrated. Time for everyone to go read some mail about File Transfer in late 2002. And Tkabber _still_ does DTCP based File Transfer instead of Bytestreams. Yay for standards. > How many test implementations of jep-secure are there? jep-secure doesn't even have a JEP number yet, hence the name. It's still stuck in the council/jep-editor void (for 3 months now). Surely an implementation is not expected. -Justin _______________________________________________ jdev mailing list [EMAIL PROTECTED] https://jabberstudio.org/mailman/listinfo/jdev
