Andy Parkins [ARCHIVE] on Nostr: 📅 Original date posted:2011-12-21 🗒️ Summary of this message: Amir Taaki ...
📅 Original date posted:2011-12-21
🗒️ Summary of this message: Amir Taaki suggests using a hierarchical method for mapping browser information, making it easier to scan all browsers using WebKit.
📝 Original message:On 2011 December 21 Wednesday, Amir Taaki wrote:
> In the original intention for BIP_0014, that would map to:
>
> /Gecko:20110613/Firefox:6.0a2/Mozilla:5.0/
>
> With something like WebKit, it becomes easy to see why that would be
> useful. You can suddenly do a network wide scan of all browsers using
> WebKit, rather than having to maintain a database of all WebKit enabled
> browsers.
This seems excellent to me.
I think most developers want to do the right thing when it comes to standards,
and it is only the inflexibility or ambiguity of a standard that means they
don't.
This heirarchical method lets every client supply all the information they
have -- nobody has to make a decision to leave something out. The internal
debate they would have "is my gui version more important than my protocol
engine version?" is unnecessary.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111221/c7b379b6/attachment.sig>
🗒️ Summary of this message: Amir Taaki suggests using a hierarchical method for mapping browser information, making it easier to scan all browsers using WebKit.
📝 Original message:On 2011 December 21 Wednesday, Amir Taaki wrote:
> In the original intention for BIP_0014, that would map to:
>
> /Gecko:20110613/Firefox:6.0a2/Mozilla:5.0/
>
> With something like WebKit, it becomes easy to see why that would be
> useful. You can suddenly do a network wide scan of all browsers using
> WebKit, rather than having to maintain a database of all WebKit enabled
> browsers.
This seems excellent to me.
I think most developers want to do the right thing when it comes to standards,
and it is only the inflexibility or ambiguity of a standard that means they
don't.
This heirarchical method lets every client supply all the information they
have -- nobody has to make a decision to leave something out. The internal
debate they would have "is my gui version more important than my protocol
engine version?" is unnecessary.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20111221/c7b379b6/attachment.sig>