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

When using purchaseticket cmd with multiple tickets, use multiple server connections #22

Open
raedah opened this issue Jun 2, 2018 · 2 comments

Comments

@raedah
Copy link
Member

raedah commented Jun 2, 2018

The current behavior is for a single connection to the server to be used per participant, even if the participant is purchasing multiple tickets. Instead, only add one splittx per connection and open multiple connections if the user is buying multiple tickets.

This is the cmd used to purchase multiple tickets with a single command.
purchaseticket default 50 0 "" 3

@huyntsgs
Copy link
Contributor

huyntsgs commented Jun 6, 2018

This will change current work flow on dcrwallet and dcrtxmatcher server. It may take a while.

@raedah
Copy link
Member Author

raedah commented Jun 7, 2018

It will be challenging to select non conflicting utxos, so this task will be a low priority.

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