- From: Johan Verrept via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Aug 2017 09:52:04 +0000
- To: public-webauthn@w3.org
@jyasskin Probably not. At this point, I see no need to use indefinite maps and arrays but this might easily change in future specs. I consider indefinite length strings essential (from authenticator to client). As for sorted maps... this type of optimization is only going to matter for really small or slow processors. Requiring this from the client is one thing, requiring the authenticator to enforce this would actually add complexity to more a generic parser (who suddenly would need to care about order). As for 16 bit processors, I have no problem just banning additional types 26 and 27 (4 and 8 byte length fields) for all major types in all directions. -- GitHub Notification of comment by jovasco Please view or discuss this issue at https://github.com/w3c/webauthn/issues/455#issuecomment-325942134 using your GitHub account
Received on Wednesday, 30 August 2017 09:52:00 UTC