Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Real Time Updates #15

Open
jardev opened this issue Oct 22, 2014 · 1 comment
Open

Real Time Updates #15

jardev opened this issue Oct 22, 2014 · 1 comment

Comments

@jardev
Copy link
Member

jardev commented Oct 22, 2014

process_transactions actually implements the 'pull'-way to synchronize transactions between Ripple network and the database. Thus we have to run this command periodically (e.g. by cron). It's inefficient, resource-intensive, slow for response. The end user should never wait even for a minute or two if a transaction has been already completed. Definitely there should be a way to update data on the fly, using some kind of a 'push'. I assume the Ripple client does exactly the same. Maybe also take a look at https://github.com/ripple/gatewayd

@akhavr
Copy link
Member

akhavr commented Oct 22, 2014

ripple_api is designed with light-weigt use in mind. Scripts, occasional IOU transfers or trades. For complete realtime integration, I'd use gatewayd api.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants