Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. The system provides, by means of a header enumeration, an abstraction that allows message headers to be treated as objects, accessible via an application program interface that supports multiple communication protocols and allows clients and servers to communicate request/response messages using any of the supported protocols. When a request message with a known header type is encountered, the system can obtain an indexed value from the enumeration, if available, and provide the associated data directly to the process to which the request is directed, and/or cache the header value for later use.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. The system provides, by means of a header enumeration, an abstraction that allows message headers to be treated as objects, accessible via an application program interface that supports multiple communication protocols and allows clients and servers to communicate request/response messages using any of the supported protocols. When a request message with a known header type is encountered, the system can obtain an indexed value from the enumeration, if available, and provide the associated data directly to the process to which the request is directed, and/or cache the header value for later use.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. The system enables configuration of a server that can operate to serve requests via multiple network or communication protocols, such as for example HTTP1, gRPC over HTTP2, and/or WebSocket. A route abstraction allows each protocol to have its own routing, e.g., an HTTP routing. A sub-abstraction can provide a more specific route, for example as an HTTP1 route, or an HTTP2 route. For a request message received via a particular protocol, the system can pick up the appropriate route for the request, and process it accordingly.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. To support testing of software applications or services, a client connection can be replaced with an in-memory implementation that exposes inverse functions to a server connection; for example, data bytes written to a data writer of a client connection are available through a data reader on a server connection, and vice versa. During testing, the in-memory implementation uses a blocking queue in memory, but without using actual sockets. Once the testing has been completed using the in-memory implementation, the client and/or server code can be tested against actual sockets, for use in processing a request.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. To support features such as client/server connection abstraction, router abstraction, or the use of different protocols on a single socket, an extensible service provider interface provides software methods that allow protocol identification for a request message and connection. When a connection request message is received from a client directed to a server, a determination is made as to whether the request can be appropriately handled. The protocol identification process can, for example, return an indication that the system does not support the request protocol, that it does not have enough data to make a decision, or that additional data is needed to make such a determination.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. The system provides, by means of a header enumeration, an abstraction that allows message headers to be treated as objects, accessible via an application program interface that supports multiple communication protocols and allows clients and servers to communicate request/response messages using any of the supported protocols. When a request message with a known header type is encountered, the system can obtain an indexed value from the enumeration, if available, and provide the associated data directly to the process to which the request is directed, and/or cache the header value for later use.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. The system enables configuration of a server that can operate to serve requests via multiple network or communication protocols, such as for example HTTP1, gRPC over HTTP2, and/or WebSocket. A route abstraction allows each protocol to have its own routing, e.g., an HTTP routing. A sub-abstraction can provide a more specific route, for example as an HTTP1 route, or an HTTP2 route. For a request message received via a particular protocol, the system can pick up the appropriate route for the request, and process it accordingly.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. To support testing of software applications or services, a client connection can be replaced with an in-memory implementation that exposes inverse functions to a server connection; for example, data bytes written to a data writer of a client connection are available through a data reader on a server connection, and vice versa. During testing, the in-memory implementation uses a blocking queue in memory, but without using actual sockets. Once the testing has been completed using the in-memory implementation, the client and/or server code can be tested against actual sockets, for use in processing a request.

Abstract: In accordance with an embodiment, described herein are systems and methods for use with a microservices or other computing environment, including a web server together with related libraries and features usable to build cloud-native applications or services. To support features such as client/server connection abstraction, router abstraction, or the use of different protocols on a single socket, an extensible service provider interface provides software methods that allow protocol identification for a request message and connection. When a connection request message is received from a client directed to a server, a determination is made as to whether the request can be appropriately handled. The protocol identification process can, for example, return an indication that the system does not support the request protocol, that it does not have enough data to make a decision, or that additional data is needed to make such a determination.

Abstract: Apparatus and methods for managing the operation of wireless communication systems are described for transferring inter-exchange information. Interdepending data pertaining to inter-exchange traffic handling events is transferred from the exchange where the data was entered in man-machine-language (MML) by a human operator to other applicable exchanges where the data is automatically entered base upon a subscription between the serving exchange and the target exchange.

Abstract: Apparatus and methods for managing the operation of wireless communication systems are described for transferring inter-exchange information. Interdepending data pertaining to inter-exchange traffic handling events is transferred from the exchange where the data was entered in man-machine-language (MML) by a human operator to other applicable exchanges where the data is automatically entered base upon a subscription between the serving exchange and the target exchange.