google-nomulus/java/google/registry/module/backend
guyben 9d2b1e7572 Consolidate all Set parameter parsing
Currently, we have two different ways to parse a "set" parameter:
key=value1&key=value2&key=value3...
and
keys=value1,value2,value3

This is error prone for several reasons:
- different parts of the code must be "synchronized" to use the same style (the
  place that creates the request, and the place that parses the request)
- for the key=value1&key=value2, we often use the same key name for the single
  value and the set value. This can result in subtle bugs where part of the
  code will successfully read the key assuming there's only one key (and will
  get the first key=value1, ignoring the rest)

Here we transition everything to the keys=value1,value2,value3 method. This one
was chosen because:
- it's shorter
- it's more intuitive for users
- the key name is plural, differentiating it from the singular key=value that
  other requests might need

-----------------------------------

To make sure there are not "transition issues", we will continue to support
(with warnings) the key=value1&key=value2 parameter parsing until we're sure we
haven't forgotten to update any part of the code.

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=198810681
2018-06-06 15:04:02 -04:00
..
BackendComponent.java Move metrics dependencies to artifacts under Maven groupId com.google.monitoring-client 2018-01-04 17:12:35 -05:00
BackendModule.java Consolidate all Set parameter parsing 2018-06-06 15:04:02 -04:00
BackendRequestComponent.java Add mapreduce to delete load test data 2018-04-10 17:07:15 -04:00
BackendRequestHandler.java Remove requireLogin action attribute 2017-06-21 10:04:05 -04:00
BackendServlet.java Migrate to Flogger (green) 2018-05-30 12:18:54 -04:00
BUILD Migrate to Flogger (green) 2018-05-30 12:18:54 -04:00
package-info.java Update copyright year on all license headers 2017-02-02 16:27:22 -05:00