You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the number of implementation grows, those tables become quite bloated. If one wants to e.g. select a client for Windows, or find a library usable on Mac OS X, then being able to filter becomes massively helpful.
I guess for platforms, there could be a popup menu with choices "Any" plus the various operating systems (of course, the information about platforms first needs to be added to the datafiles, see issue #4); for client/server it could be checkboxes or a popup with "don't care", "client", "server", "client & server"; etc.
(Of course one might also argue that clients and servers should be shown on separate pages in the first place, and also libraries vs. standalone, etc., but sometimes it is also useful to see all implementation on a single page, to determine whether a given protocoll is widely available or not).
This could probably be implemented in pure JavaScript.
The text was updated successfully, but these errors were encountered:
As an extended version of this, one may also wish to allow restricting the comparison to specific set of implementations (i.e. allow head-on-head comparision of 2-N implementations), and also to a specific set of protocols. E.g. on may want to compare a set of available clients, and see which of these support aes128-ctr and diffie-hellman-group14-sha1.
But perhaps this would complicate the UI needlessly... might be better to see and wait if anybody requests that ;-)
As the number of implementation grows, those tables become quite bloated. If one wants to e.g. select a client for Windows, or find a library usable on Mac OS X, then being able to filter becomes massively helpful.
I guess for platforms, there could be a popup menu with choices "Any" plus the various operating systems (of course, the information about platforms first needs to be added to the datafiles, see issue #4); for client/server it could be checkboxes or a popup with "don't care", "client", "server", "client & server"; etc.
(Of course one might also argue that clients and servers should be shown on separate pages in the first place, and also libraries vs. standalone, etc., but sometimes it is also useful to see all implementation on a single page, to determine whether a given protocoll is widely available or not).
This could probably be implemented in pure JavaScript.
The text was updated successfully, but these errors were encountered: