David Snopek authored 12 years ago and Justus Luthy committed 12 years ago

When using the default exchange (if undefined in publish), we don't need
to redefine it.

 * Got amqp.queue.inc worked to consume messages.

Previously, all users were binding to #, making them get all messages.
Now, if one implements the amqp_nodejs_routing_keys hook, it allows the
javascript to listen on multiple routing keys defined by the hook.

INSTALL.txt needs to specify that we cannot be on master while
installing rabbitmq-c, and thus we need to switch to the 1.0 branch
before proceeding.

More API doc cleanup. Moved functions into amqp.api.php and left instructions in API.txt for easier maintenance.

Instead of simply returning amqp_consumers hook values, we should
format the contents a bit to make it interact nicely with the
python consumer daemon.

Adds a basic python REST listeter than can be configured with a YAML
file.  There's a basic yml file provided, but it probably won't suit
most peoples' needs.  Customize it to your pleasure, or just wait until
this project has a yaml builder.  We may also go a different way with
arg parsing or something cooler when we kick the restbot off via some
sort of Drupal exec.

Install instructions for the python piece assume you have python
installed, As with the rest of this project, the python piece is pretty
alpha.  It should work, but we have yet to beat on it with a thousand
golden hammers.

Have an ice day!

update amqp_services resources to allow consumers to send a message to Drupal. Paired with the NodeJS consumer, we can also provide user-level notification messages as well as (now) the back-end server side processing. Also, since it's handled in a separate http request it doesn't slow things down as bad.

 * rename consumer to consumers to better reflect what we are implementing.

 * Update APIs so arguments are 'optional', move to last argument so we don't have to supply an empty array when defining exchanges, etc.
 * Add 'default' callback handler with error message.
 * Add more api documentation so developers can leverage our callbacks. Keep in mind this is still alpha so things might change.

use register_shutdown_function instead of drupal_register_shutdown_function (latter not implemented until Drupal 7)

* Add amqp_installed method to verify that we can get a connection (AMQP PHP extension installed).
* add 'Test Connection' button to admin form so we can verify a message published and consumed through AMQP.

* add exception handling so things don't explode as bad if php AMQP isn't installed.

Changed the nodejs client to connect to the correct url.
Changed the nodejs client to trigger an event when a message is received.