Using a Response Server

From Videntity Documentaion Wiki

When a transaction is sent to Videntity using HTTP POST, the server responds with an XML 'respopnse' document. The response contains, among other things, a status code indicating 'SUCCESS', 'PENDING', or 'FAIL'. Some transactions complete immediately while other transactions (i.e transactions waiting for a phone call to be answered) go into a PENDING status.

When Videntity initially responds to a transaction, a transaction_id is provided to allow you to track your pending transactions. A Response Server is simply any HTTPS daemon/server that can accept response update information from the Videntity Server so it listens to accept transaction update information. In other words, this prevents the need to poll for responses updates.

You can create your own response server or you can use the open source one provided. The response information is sent using HTTP POST. A Response Server's database only needs a single table or flat file. The design of the response server's response data lends itself to taking advantage of object databases such as BigTable and Amazon SimpleDB.