The objective of spire.io is to allow developers to build Web and mobile applications without having to also build the server-side infrastructure that is typically needed to support them. The server-side support provided by spire.io is centered upon providing infrastructure for developers through RESTful API's and scenario-specific client libraries.
The fundamental building blocks of spire.io's back-end support services are their channel and subscription resources, which essentially provide the backbone for communication and event listeners within the spire.io infrastructure.
Spire.io currently has two available services; Messaging, which provides the foundation of real-time capabilities to applications; and Identity, which allows developers to easily integrate user registration and log-in into their apps.
The following is a list of historical changes that were made to this asset. Typically,
once an API is published on ProgrammableWeb.com, the data we keep about that asset gets updated over the course of its life. For example, the endpoint or home page of the documentation might change.
As a means of enforcing the integrity of our data, every time a non-trivial change is made to the data we keep about an asset,
we require the entry of some changelog text before that change can be saved. This way, we have a great audit trail of all
activity surrounding the asset. For each asset, the changelogs begins with the moment an asset is approved for publication on ProgrammableWeb.
If you spot an error in our data and believe that a record needs to be updated in some way,
the ProgrammableWeb team would very much like to hear from you at firstname.lastname@example.org