Skip to content
This repository has been archived by the owner on Jan 3, 2019. It is now read-only.

Internal XMLHttpRequest Error #239

Open
2 of 5 tasks
ghost opened this issue Jul 16, 2015 · 5 comments
Open
2 of 5 tasks

Internal XMLHttpRequest Error #239

ghost opened this issue Jul 16, 2015 · 5 comments
Assignees

Comments

@ghost
Copy link

ghost commented Jul 16, 2015

Consolidating all issues related to timeouts, XMLHttpRequest Error ( #233 ) etc in this issue and closing the rest.

  • Reduce network payload
  • Open the wallet as soon as all the used addresses are discovered. At this point we have the balance. User can see the balance, but not the transaction history, and they will not be able to spend any money.
  • Fetch all the unspents for the discovered addresses. After this is done, user will be able to send money.
  • Load transactions. Given the limitation of blockr, we cannot query transactions by block height for a given set of addresses, so there's no sure way to load the latest transactions first. Our best bet is to load the transactions in order of the newest discovered to the first discovered addresses. In UX words, 1) it's not possible to load the latest n transactions first, then wait for user to scroll to load more, while guarantee correctness. 2) if we decide to show transactions as they come in, transactions will come in no particular order -- you will see transactions inserted in between already loaded transactions, if we want to preserve the current reverse chronological order in the history tab. Whether we want to show transactions as they come in or show nothing until all transactions are loaded, that's a UX decision I'll leave to @mattatgit
  • Serialize the previous instance of the wallet to browser db. We should always assume that balance and unspents are out of date. Only show transactions from the old wallet, until we have updated transaction data.
@ghost ghost assigned weilu Jul 16, 2015
@ghost ghost changed the title Reduce payload of wallet API Reduce wallet payload (API connection issue) Jul 16, 2015
@ghost ghost removed the high label Jul 16, 2015
@Dazzr
Copy link

Dazzr commented Jul 16, 2015

Passphrase entered in http://hive-js.herokuapp.com .. And then? Something more needed?

@ghost
Copy link
Author

ghost commented Jul 16, 2015

@Dazzr and... what happened? Did it work/open your wallet?

@weilu weilu changed the title Reduce wallet payload (API connection issue) Internal XMLHttpRequest Error Jul 17, 2015
@dnldd
Copy link

dnldd commented Jul 17, 2015

having the same issue here, tried http://hive-js.herokuapp.com and still getting that error.

@losh11
Copy link

losh11 commented Sep 27, 2015

Hive was working until now, was trying to check if loading times were faster (from Heroku) - but kept on getting this when trying to sync, I also created a new wallet just to check, got the same error.

@Schamns
Copy link

Schamns commented Jan 5, 2016

I just can't access my wallet anymore! even with the android app. Please fix this problem! I'm desperate!

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

No branches or pull requests

5 participants