abstracts out the long-polling mechanism for usage in any endpoint through use of route handlers:
getData: to get the relevant data for the endpoint, route parameters, and query parameters given
getPaginatedResponse: to format the data into pages of output payload for the given query parameters
it should format pages based on given pagination query parameters (eg. pagination.limit=100)
adds an additional mechanism: "server-side events" or SSE for a more efficient method of data updates (when supported by the networking transport layer (using HTTP/2), and requested specifically from the using the query parameter streaming=true
This PR update:
getData
: to get the relevant data for the endpoint, route parameters, and query parameters givengetPaginatedResponse
: to format the data into pages of output payload for the given query parameterspagination.limit=100
)streaming=true
SSL_PRIVATE_KEY_FILE
: file path of the private PEM keySSL_PUBLIC_KEY_FILE
: file path of the public PEM key orSSL_PRIVATE_KEY
: the text of the private PEM keySSL_PUBLIC_KEY
: the text of the public PEM key