The Animoto API is a RESTful web service that transforms images, videos, music, and text into amazing video presentations. The Animoto API Ruby Client provides a convenient Ruby interface for working with the Animoto RESTful HTTP API.

The Deltacloud API is built as a service-based REST API. You do not directly link a Deltacloud library into your program to use it. Instead, a client speaks the Deltacloud API over HTTP to a server which implements the REST interface.

HTTP persistent connection support for ActiveResource

Catch all of them Net::HTTP timeout errors

NxtHttpClient allows you to easily create and configure http clients.

Egregious is a rails based exception handling gem for well defined http exception handling for json, xml and html. Requires Rails.

Log HTTP requests made via Excon and their total runtime in Rails request log.

Small wrapper (using httparty, etc.) to provide an interface that mimicks AR main methods using a REST API

The APIMatic Core libraries provide a stable runtime that powers all the functionality of SDKs. This includes functionality like the ability to create HTTP requests, handle responses, apply authentication schemes, convert API responses back to object instances, and validate user and server data.

This gem works mostly as HTTParty, but has automatic saving and sending of cookies to the server.

HTTP dashboard for the distributed event system Riemann.

Faraday is a simple, yet elegant, HTTP library. This repository contains the client implementation that uses the requests library for python SDK provided by APIMatic.

Parse and represent UID tokens from Apache's mod_uid / nginx's ngx_http_userid_module in Ruby.

A gem for handling exceptions thrown inside your Rails app. If you include the gem in your application controller, wrangler will render the error pages you configure for each exception or HTTP error code. It will also handle notifying you via email when certain exceptions are raised. Allows for configuration of which exceptions map to which error pages, which exceptions result in emails being sent. Also allows for asynchronous email sending via delayed job so that error pages don't take forever to load (but delayed_job is not required for sending email; wrangler will automatically send email synchronously if delayed_job is not available. . See README for lots of info on how to get started and what configuration options are available.

Allows customization of: * Specify which level of notification you would like with an array of optional styles of notification (email, webhooks) * the sender address of the email * the recipient addresses * the text used to prefix the subject line * the HTTP status codes to notify for * the error classes to send emails for * alternatively, the error classes to not notify for * whether to send error emails or just render without sending anything * the HTTP status and status code that gets rendered with specific errors * the view path to the error page templates * custom errors, with custom error templates * define error layouts at application or controller level, or use the controller's own default layout, or no layout at all * get error notification for errors that occur in the console, using notifiable method * Override the gem's handling and rendering with explicit rescue statements inline. * Hooks into `git blame` output so you can get an idea of who (may) have introduced the bug * Hooks into other website services (e.g. you can send exceptions to to Switchub.com) * Can notify of errors occurring in any class/method using notifiable { method } * Can notify of errors in Rake tasks using NotifiedTask.new instead of task * Works with Hoptoad Notifier, so you can notify via SEN and/or Hoptoad for any particular errors. * Tested with Rails 2.3.x, should work with rails 2.2.x, and is apparently not yet compatible with rails 3.

EventMachine-LE (Live Edition) is a branch of EventMachine (https://github.com/eventmachine/eventmachine). This branch incorporates interesting pull requests that are not yet included in the mainline EventMachine repository. The maintainers of that version prefer to minimize change in order to keep the stability with already existing EventMachine deployments, which provides an impressive multi-platform base for IPv4 TCP servers (e.g., Web servers) that don't need good UDP or IPv6 support. This dedication to stability is helpful for production use, but can also lead to ossification. The present "Live Edition" or "Leading Edge" branch has its focus on supporting a somewhat wider use, including new Web servers or protocols beyond the HTTP Web. To provide even more focus, this branch is currently applying its energy towards Linux and Unix/BSD/OSX environments. Java reactor and pure Ruby reactor are for now removed in this branch, and Windows/Cygwin support is untested. This may very well change later, once interesting pull requests come in. EventMachine-LE draws from a number of dormant pull requests on the mainline version of EventMachine. New proposals will also directly come to EventMachine-LE and will be included once they are tested. This is not a "development branch", EventMachine-LE is ready for production, just beyond the focus of mainline EventMachine.

email => http post

code,tfile,pager,http,logistic,pay,tmagick,class_extend,aes,rsa,ftp_tool,translate,zip_tool,sql,backup,collection;

rack-facebook is a Rack middleware that checks the signature of Facebook params, and converts them to Ruby objects when appropiate. Also, it converts the request method from the Facebook POST to the original HTTP method used by the client.

Wrapper for Faraday with additional functionality