Search Results for "aim"

Most modern networking is built either on slow and ambiguous REST APIs or unnecessarily complex gRPC. FastAPI, for example, looks very approachable. We aim to be equally or even simpler to use. It takes over a millisecond to handle a trivial FastAPI call on a recent 8-core CPU. In that time, light could have traveled 300 km through optics to the neighboring city or country, in my case. How does UCall compare to FastAPI and gRPC? How can a tiny pet-project with just a couple thousand lines of code compete with two of the most established networking libraries? ...

httr is superseded: only changes necessary to keep it on CRAN will be made. We recommend using httr2 instead. The aim of httr is to provide a wrapper for the curl package, customized to the demands of modern web APIs. Functions for the most important http verbs: GET(), HEAD(), PATCH(), PUT(), DELETE() and POST(). Automatic connection sharing across requests to the same website (by default, curl handles are managed automatically), cookies are maintained across requests, and an up-to-date root-level SSL certificate store is used. ...

...There are a thousand one-week projects that barely work when all we need is one real project. One project was done right. We are the ones who are going to do this right. Our aim is to solve the problem of unreliable file uploads once and for all. tus is a new open protocol for resumable uploads built on HTTP. It offers simple, cheap, and reusable stacks for clients and servers. It supports any language, any platform, and any network. It may seem to be an impossible dream. Perhaps that is because no-one has managed to solve it yet. ...

A NodeJS based webserver that polls your nagios server for state information and provides ajax-like updates to a web browser. The aim is to provide a single nagios operational overview screen that is useful on wall-mounted displays.

WYMIWYG KnoBot is a content management system for the semantic web designed to promote the exchange of content with a P2P and reputation based system. The aim is to create a socio-topical space, a perspective dependent space of information and knowledge.

Incredibly versatile distributed filesystem. The aim of this project is to provide a FUSE filesystem capable of transparent multi-master, replication and raid-like behavior.

The aim of pServ (pico Server) is to create a portable, small webserver. Coded in portable C with Unix being the main reference platform, but porting is encouraged. Portability and small footprint should enable the use of pServ on a workstation as well as

"mod_auth_cache" is an authentication caching module for Apache webservers, which uses session cookies to transparently cache a users authentication, which was initially done by a different module. Another aim is to allow single-signon in a domain.

an internet chat++ server, providing access through many interfaces, currently planning to use the following: IRC(s), HTTP(s), ssh, telnet(s), msn, aim, yahoo, icq, jabber(s), and custom clients

The aim of this project is to develop a P3P- and APPEL-compliant user agent. P3P and APPEL are two specifications of the W3C concerned with privacy issues (http://www.w3.org/P3P).