* <p>On the other hand, if for example we are resolving {@code List<A extends B>} to {@code
   * List<A extends String>}, we need to compare that {@code <A extends B>} is unequal to {@code <A
   * extends String>} in order to decide to use the transformed type instead of the original type.
   */
  static final class TypeVariableKey {
    private final TypeVariable<?> var;

    TypeVariableKey(TypeVariable<?> var) {

        percentIndex = i;
        break;
      } else if (Character.digit(c, 16) == -1) {
        return null; // Everything else must be a decimal or hex digit.
      }
    }

    // Now decide which address family to parse.
    if (hasColon) {
      if (hasDot) {
        ipString = convertDottedQuadToHex(ipString);
        if (ipString == null) {
          return null;
        }
      }

labels.loginLink=顯示登入連結
labels.threadName=執行緒名稱
labels.url=URL
labels.userFavorite=收藏日誌
labels.userInfo=使用者資訊
labels.webApiJson=JSON響應
labels.webConfigName=Web爬網配置名稱
labels.allLanguages=所有語言
labels.dictId=字典ID
labels.docId=文檔ID
labels.endTime=結束時間
labels.hq=hq
labels.inputs=輸入
labels.jobLogging=日誌記錄
labels.jobName=名稱
labels.jobStatus=狀態
labels.labelTypeIds=標籤
labels.lang=語言
labels.outputs=輸出
labels.pos=詞性

I'll tell you a bit more about these **concepts** here, and that would hopefully give you the **intuition** you would need to decide how to deploy your API in very different environments, possibly even in **future** ones that don't exist yet.

By considering these concepts, you will be able to **evaluate and design** the best way to deploy **your own APIs**.

labels.userFavorite=Favoritenprotokoll
labels.userInfo=Benutzerinformationen
labels.webApiJson=JSON-Antwort
labels.webConfigName=Webcrawl-Konfigurationsname
labels.allLanguages=Alle Sprachen
labels.dictId=Wörterbuch-ID
labels.docId=Dokument-ID
labels.endTime=Endzeit
labels.hq=hq
labels.inputs=Eingaben
labels.jobLogging=Protokollierung
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=Sprache

Então, quando é sua vez, você faz trabalho realmente "produtivo", você processa o menu, decide o que quer, pega a escolha de seu _crush_, paga, verifica se entregou o cartão ou a cédula correta, verifica se foi cobrado corretamente, verifica se seu pedido está correto etc.

Now let's **refactor** this app a bit to increase **security** and **versatility**.

If you check the previous app, in the UI you can see that, up to now, it lets the client decide the `id` of the `Hero` to create. 😱

We shouldn't let that happen, they could overwrite an `id` we already have assigned in the DB. Deciding the `id` should be done by the **backend** or the **database**, **not by the client**.

labels.userInfo=Informacje o użytkowniku
labels.webApiJson=Odpowiedź JSON
labels.webConfigName=Nazwa konfiguracji indeksowania stron internetowych
labels.allLanguages=Wszystkie języki
labels.dictId=ID słownika
labels.docId=ID dokumentu
labels.endTime=Godzina zakończenia
labels.hq=hq
labels.inputs=Wejścia
labels.jobLogging=Logowanie
labels.jobName=Nazwa
labels.jobStatus=Status
labels.labelTypeIds=Etykiety
labels.lang=Język

    }
    assertNull(map.get(unmappedKey));
  }

  public void testGetNull() {
    Map<K, V> map = makeEitherMap();
    if (allowsNullKeys) {
      if (allowsNullValues) {
        // TODO: decide what to test here.
      } else {
        assertEquals(map.containsKey(null), map.get(null) != null);
      }
    } else {
      try {
        V unused = map.get(null);

labels.userFavorite=Журнал избранного
labels.userInfo=Информация о пользователе
labels.webApiJson=Ответ JSON
labels.webConfigName=Имя конфигурации веб-сканирования
labels.allLanguages=Все языки
labels.dictId=ID словаря
labels.docId=ID документа
labels.endTime=Время окончания
labels.hq=hq
labels.inputs=Входы
labels.jobLogging=Ведение журнала
labels.jobName=Имя
labels.jobStatus=Статус
labels.labelTypeIds=Метки
labels.lang=Язык