Biblioteca para simular um backend em tempo de excução diretamente no browser.
A Javascript library for running ONNX models on browsers
Use react-devtools outside of the browser
Firebase JavaScript library for web and Node.js
AWS SDK for JavaScript Lambda Client for Node.js, Browser and React Native
Core API used by Backstage backend plugins
Simple to use, blazing fast and thoroughly tested websocket client and server for Node.js
Hardware-accelerated JavaScript library for machine intelligence
Clerk Backend SDK - REST Client for Backend API & JWT verification utilities
AWS credential provider that calls STS assumeRole for temporary AWS credentials
Amazon Cognito Identity Provider JavaScript SDK
Web Push library for Node.js
Stringify JS values
Core API used by Backstage backend apps
Multi Backend system compatible with React DnD
backend layer for i18next using browsers fetch
Implements the WebIDL algorithms for converting to and from JavaScript values
A native "Headers" class polyfill.
Appwrite is an open-source self-hosted backend server that abstracts and simplifies complex and repetitive development tasks behind a very simple REST API
Portable Unix shell commands for Node.js
i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
Toast components for the Courier web UI
An open-source machine learning framework.
A filesystem, anywhere
HTTP::Cookie is a Ruby library to handle HTTP Cookies based on RFC 6265. It has with security, standards compliance and compatibility in mind, to behave just the same as today's major web browsers. It has builtin support for the legacy cookies.txt and the latest cookies.sqlite formats of Mozilla Firefox, and its modular API makes it easy to add support for a new backend store.
Firebase is a real time backend to allow clients to sharedata on the web. This gem provides a ruby API implementation.
Firebase is a real time backend to allow clients to sharedata on the web. This gem provides a ruby API implementation.
This is the start of a Puppet provisioning system. It provides a graphical web service, a JSON rest API and command line interface that will manage Hiera YAML files and a few functions to read them and apply classes and parameters to a node. It works like a lightweight External Node Classifier. It also provides provisioning functionality to spin up new instances after classifying them. It currently has a backend for Cloud Provisioner and will shortly have a VMWare plugin to spin up new instances for Razor to provision. New backend plugins are quite easy to create. Documentation forthcoming.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
RSence is a different and unique development model and software frameworks designed first-hand for real-time web applications. RSence consists of separate, but tigtly integrated data- and user interface frameworks. RSence could be classified as a thin server - thick client system. Applications and submobules are installed as indepenent plugin bundles into the plugins folder of a RSence environment, which in itself is a self-contained bundle. A big part of RSence itself is implemented as shared plugin bundles. The user interface framework of RSence is implemented in high-level user interface widget classes. The widget classes share a common foundation API and access the browser's native API's using an abstracted event- and element layer, which provides exceptional cross-browser compatibility. The data framework of RSence is a event-driven system, which synchronized shared values between the client and server. It's like a realtime bidirectional form-submission engine that handles data changes intelligently. On the client, changed values trigger events on user interface widgets. On the server, changed values trigger events on value responder methods of server plugin modules. It doesn't matter if the change originates on client or server, it's all synchronized and propagated automatically. The server framework is implemented as a high-level, modular data-event-driven system, which handles delegation of tasks impossible to implement using a client-only approach. Client sessions are selectively connected to other client sessions and legacy back-ends via the server by using the data framework. The client is written in Javascript and the server is written in Ruby. The client also supports CoffeeScript for custom logic. In many cases, no custom client logic is needed; the user interfaces can be defined in tree-like data models. By default, the models are parsed from YAML files, and other structured data formats are possible, including XML, JSON, databases or any custom logic capable of producing similar objects. The server can connect to custom environments and legacy backends accessible on the server, including software written in other languages.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.