Search Results for "http file server"

Sangria is a Scala GraphQL implementation. It is an example of GraphQL server written with Play framework and Sangria. It also serves as a playground, where you can interactively execute GraphQL queries and play with some examples. If you want to use sangria with a react-relay framework, then you also may be interested in sangria-relay. Sangria is a spec-compliant GraphQL implementation, so it works out of the box with Apollo, Relay, GraphiQL and other GraphQL tools and libraries. Since...

Declarative, type-safe web endpoints library. With tapir, you can describe HTTP API endpoints as immutable Scala values. Each endpoint can contain a number of input and output parameters. Compile-time guarantees, develop-time completions, read-time information. Separate the shape of the endpoint (the "what"), from the server logic (the "how"). Generate documentation from endpoint descriptions. Leverage the metadata to report rich metrics and tracing information.

...Schemas are type safe and derived at compile time. No need to manually define a schema for every type in your API. Let the compiler do the boring work. Out-of-the-box support for major HTTP server libraries, effect types, Json libraries and more.

...It compares implementations built with frameworks and runtimes such as Spray, Netty, Undertow, Jetty, Vert.x, Grizzly, Node.js, Go, and Go-fasthttp. The project focuses on large-scale long-lived WebSocket connections and documents tests reaching more than one million active connections. It includes simple server prototypes that can act as scaffolds for chat, message pushing, notification, or real-time delivery systems. The repository also provides deployment and tuning guidance for servers, clients, memory settings, file descriptor limits, and multiple test IPs. It is useful for engineers evaluating WebSocket stack behavior under extreme connection pressure.

Spray is a suite of Scala libraries built on top of Akka that offers a modular, asynchronous, and non-blocking toolkit for building and consuming RESTful and HTTP services. The core philosophy behind Spray is that it should act as a “library” for integration and HTTP layers, not as a full application framework—it gives you the building blocks to handle HTTP and REST but doesn’t impose heavy structure. It includes modules for low-level HTTP I/O, routing, client and server APIs, HTTP model (requests/responses), (un)marshalling, servlet adapters, and testing utilities. ...