WebSocket.request(long n) should not accept 0

XMLWordPrintable

    • Type: Bug
    • Resolution: Not an Issue
    • Priority: P4
    • None
    • Affects Version/s: 9
    • Component/s: core-libs
    • generic
    • generic

      0 looks to be a meaningless value for n, but it is allowed now. If no message is planned to request, why invoke this method.

      It looks reasonable to throw IllegalArgumentException for 0

            Assignee:
            Pavel Rappo
            Reporter:
            Xiaofeng Yang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: