ocean-rails

ocean-rails

== Ocean Ocean is an architecture for creating server-oriented architectures (SOAs) in the cloud. It consists of two separate parts which can be used separately or in conjunction: Ocean and OceanFront. Ocean is a complete and very scalable back end solution for RESTful JSON web services and web applications, featuring aggressive caching and full HTTP client abstraction. Ocean fully implements HATEOAS principles, allowing the programming object model to move fully out onto the net, while maintaining a very high degree of decoupling. Ocean is also a development, staging and deployment pipeline featuring continuous integration and testing in a TDD and/or BDD environment. Ocean can be used for continuous deployment or for scheduled releases. Front end tests are run in parallel using a matrix of operating systems and browser types. The pipeline can very easily be extended with new development branches and quality assurance environments with automatic testing and deployment. OceanFront is a cross-platform Javascript front end browser client library supporting all major browsers and platforms. OceanFront is object oriented, widget-based and HTML-less. Together, Ocean and OceanFront allow you to write front end code completely independent of browser type and client OS, and back end code completely agnostic of whether it is called by a client browser or another server system.

Rubygem ocean-rails

Total Downloads
27565
Releases
124
Current Version
2.10.5
Released
2014-04-16 00:00:00 UTC
First Release
2013-08-13 00:00:00 UTC
Depending Gems
0

Github OceanDev/ocean-rails

Watchers
1
Forks
2
Development activity
Active
Last commit
2014-04-16 08:58:15 UTC
First commit
Top contributors
Contributors
2
Issues

Resources

There are no resources yet, be the first to submit one!

Comments

There are no comments yet, be the first to write one!

Post a comment

Markdown supported
or
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.