off = (off & 0xFFFF) - this.converter;
            off = start + off;
            e.commentOrMasterBrowser = readString(buffer, off, 48, false);

            if (log.isTraceEnabled()) {
                log.trace(e.toString());
            }
        }
        setResults(results);
        this.lastName = e == null ? null : e.name;
        return bufferIndex - start;
    }

    @Override

Một trong những:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...và một trong những cái còn lại:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

Trong giao thức HTTP, bạn có thể giao tiếp trong mỗi đường dẫn sử dụng một (hoặc nhiều) trong các "phương thức này".

---

		adminRouter.Methods(http.MethodPost).Path(adminVersion + adminAPIClientDevExtraTime).HandlerFunc(adminMiddleware(adminAPI.ClientDevNullExtraTime, noGZFlag))

		// HTTP Trace
		adminRouter.Methods(http.MethodGet).Path(adminVersion + "/trace").HandlerFunc(adminMiddleware(adminAPI.TraceHandler, noObjLayerFlag))

		// Console Logs

			default:
				// There was error in the REST request, retry after sometime as probably the peer is down.
				time.Sleep(5 * time.Second)
			}
		}
	}()
}

// Trace - send http trace request to peer nodes
func (client *peerRESTClient) Trace(ctx context.Context, traceCh chan<- []byte, traceOpts madmin.ServiceTraceOpts) {
	go func() {
		for {
			// Blocks until context is canceled or an error occurs.

"Operation" here refers to one of the HTTP "methods".

One of:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...and the more exotic ones:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

In the HTTP protocol, you can communicate to each path using one (or more) of these "methods".

---

When building APIs, you normally use these specific HTTP methods to perform a specific action.

        //
        // Note that there is a race condition here which can result in missing
        // a cyclic edge: it's possible for two threads to simultaneous find
        // "safe" edges which together form a cycle. Preventing this race
        // condition efficiently without _introducing_ deadlock is probably
        // tricky. For now, just accept the race condition---missing a warning

    /**
     * The name or type of the error that occurred.
     * This field provides a categorization of the failure type.
     */
    public String errorName;

    /**
     * The detailed error log or stack trace for the failure.
     * This field contains the full error information for debugging purposes.
     */
    public String errorLog;

    /**
     * The number of times this URL has failed.

        // Verify
        assertNotNull(deserialized);
        assertNull(deserialized.getMessage());
        assertNull(deserialized.getCause());
    }

    public void test_stackTrace() {
        // Test that stack trace is properly maintained
        DictionaryExpiredException exception = new DictionaryExpiredException();
        StackTraceElement[] stackTrace = exception.getStackTrace();

        assertNotNull(stackTrace);

        // Both instances should be of the same class
        assertEquals(exception1.getClass(), exception2.getClass());
    }

    public void test_stackTrace() {
        // Test that the exception has a proper stack trace
        FessUserNotFoundException exception = new FessUserNotFoundException("testuser");

        StackTraceElement[] stackTrace = exception.getStackTrace();
        assertNotNull(stackTrace);

"Операція" (operation) тут означає один з "методів" HTTP.

Один з:

* `POST`
* `GET`
* `PUT`
* `DELETE`

...та більш екзотичних:

* `OPTIONS`
* `HEAD`
* `PATCH`
* `TRACE`

У HTTP-протоколі можна спілкуватися з кожним шляхом, використовуючи один (або кілька) з цих "методів".

---

При створенні API зазвичай використовуються конкретні методи HTTP для виконання певних дій.