Author Topic: OPENPOS :: Smartcoins Point Of Sale (POS) & BitShares Wallet for Android/iPhone  (Read 60259 times)

0 Members and 1 Guest are viewing this topic.

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
I will be uploading the alpha 9 release of the mobile wallet by this friday. Tons of UI stuff, qr code fixes are done now, making some tweaks to the send screen too, to allow for ideas that i had the odoo team add into the pos systems. "Overdraft Protection" will have to come in v1.1 or v1.2 as it was just too much code to cram into v1.0.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline mike623317

  • Hero Member
  • *****
  • Posts: 637
    • View Profile
Excellent ken

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Thanx guys. :)
 
Question: Ok, so it has come to my attention that the mobile app will suck up over 400MB if left open for 20+ minutes, this is not good. The nice thing is that this is a real-time wallet, no refresh is needed- Watch the block number in the bottom right corner. When someone sends you some money it shows up in the normal 3 seconds. Thing is, that real-time connection is sucking up my data plan! This friday (2 more days) I will be uploading the alpha 9 release and it has the 3 minute auto-close feature working. That will help *limit* data usage, but leaving your mobile wallet open for even 3 minutes might STILL suck up around 60MB grrrr - anybody have any idea why the socket is eating so much data? Is it downloading a frign movie or something? wtf
 
[member=11456]svk[/member] [member=12639]valzav[/member] [member=120]xeroc[/member] Any ideas on how I can limit the data usage?
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline ebit

  • Committee member
  • Hero Member
  • *
  • Posts: 1845
    • View Profile
  • BitShares: ebit
telegram:ebit521
https://weibo.com/ebiter

Offline svk

Thanx guys. :)
 
Question: Ok, so it has come to my attention that the mobile app will suck up over 400MB if left open for 20+ minutes, this is not good. The nice thing is that this is a real-time wallet, no refresh is needed- Watch the block number in the bottom right corner. When someone sends you some money it shows up in the normal 3 seconds. Thing is, that real-time connection is sucking up my data plan! This friday (2 more days) I will be uploading the alpha 9 release and it has the 3 minute auto-close feature working. That will help *limit* data usage, but leaving your mobile wallet open for even 3 minutes might STILL suck up around 60MB grrrr - anybody have any idea why the socket is eating so much data? Is it downloading a frign movie or something? wtf
 
[member=11456]svk[/member] [member=12639]valzav[/member] [member=120]xeroc[/member] Any ideas on how I can limit the data usage?

If you're using the websocket connection as is from the witness_node you'll get spammed with loads of object updates that you have no interest in. Your best bet would be to implement a data layer that would filter the objects coming from the witness node and then only send out updates to items that actually interest you.

For some reason on every new block the 2.4.33 or 2.4.34 objects get pushed from the witness_node, and it's a HUGE object containing feed data for every single asset. If you can filter out that you should be fine...

Worker: dev.bitsharesblocks

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Thanx guys. :)
 
Question: Ok, so it has come to my attention that the mobile app will suck up over 400MB if left open for 20+ minutes, this is not good. The nice thing is that this is a real-time wallet, no refresh is needed- Watch the block number in the bottom right corner. When someone sends you some money it shows up in the normal 3 seconds. Thing is, that real-time connection is sucking up my data plan! This friday (2 more days) I will be uploading the alpha 9 release and it has the 3 minute auto-close feature working. That will help *limit* data usage, but leaving your mobile wallet open for even 3 minutes might STILL suck up around 60MB grrrr - anybody have any idea why the socket is eating so much data? Is it downloading a frign movie or something? wtf
 
[member=11456]svk[/member] [member=12639]valzav[/member] [member=120]xeroc[/member] Any ideas on how I can limit the data usage?

If you're using the websocket connection as is from the witness_node you'll get spammed with loads of object updates that you have no interest in. Your best bet would be to implement a data layer that would filter the objects coming from the witness node and then only send out updates to items that actually interest you.

For some reason on every new block the 2.4.33 or 2.4.34 objects get pushed from the witness_node, and it's a HUGE object containing feed data for every single asset. If you can filter out that you should be fine...

Ok, so I'm not crazy, this is good stuff :)
Do you guys have any code examples of how we might implement these filters so we can keep data usage at a bare minimum? Thanx!
 
edit: i'm thinkin that in part this is also a reason why the responsiveness seems sluggish to me. the footprint is massive with all these objects you mentioned getting processed.
« Last Edit: January 27, 2016, 02:46:29 pm by kenCode »
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
nothing you can do on your end since you have to receive the data before you can filter it ..
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
ah snap, so then maybe we need to add something to the settings screen that forces wifi conn first, then if enabled, will try for mobile conn as a backup.
 
seriously there's no way to reduce the data usage at all then? :-X
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
Smartcoins POS for Odoo - Milestone 1 of 5 completed:
https://www.youtube.com/watch?v=GMECm8bqKaE&index=5&list=PLjbx3qSmDe7RYkRMIEuFyYyG7_vvKgou0
 
I'll try to have Milestone 2 of 5 done in the next couple weeks.
 
In the meantime, mobile wallets alpha 9 release will be out this friday (in 2 days), see comments above for details.
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline svk

nothing you can do on your end since you have to receive the data before you can filter it ..
No there is, what I'm saying is he needs to filter the outgoing data from the witness node using a proxy server. A node websocket server using socket.io should do the trick. He would need to host his own witness_node then obviously.
Worker: dev.bitsharesblocks

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
nothing you can do on your end since you have to receive the data before you can filter it ..
No there is, what I'm saying is he needs to filter the outgoing data from the witness node using a proxy server. A node websocket server using socket.io should do the trick. He would need to host his own witness_node then obviously.

So, I would need to have the mobile wallets all connect to one dedicated witness node? Could we just have a few/all of the Witnesses provide this as an option to their service? So, for mobile clients, the Witnesses will only serve up just the filtered stuff? Heck, this might be a great value-add for all Witnesses, no? Many more mobile wallets will be released after our I'm sure. Thoughts?
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4516
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
nothing you can do on your end since you have to receive the data before you can filter it ..
No there is, what I'm saying is he needs to filter the outgoing data from the witness node using a proxy server. A node websocket server using socket.io should do the trick. He would need to host his own witness_node then obviously.

So, I would need to have the mobile wallets all connect to one dedicated witness node? Could we just have a few/all of the Witnesses provide this as an option to their service? So, for mobile clients, the Witnesses will only serve up just the filtered stuff? Heck, this might be a great value-add for all Witnesses, no? Many more mobile wallets will be released after our I'm sure. Thoughts?
Sounds like a paid service? Interesting..
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline svk

nothing you can do on your end since you have to receive the data before you can filter it ..
No there is, what I'm saying is he needs to filter the outgoing data from the witness node using a proxy server. A node websocket server using socket.io should do the trick. He would need to host his own witness_node then obviously.

So, I would need to have the mobile wallets all connect to one dedicated witness node? Could we just have a few/all of the Witnesses provide this as an option to their service? So, for mobile clients, the Witnesses will only serve up just the filtered stuff? Heck, this might be a great value-add for all Witnesses, no? Many more mobile wallets will be released after our I'm sure. Thoughts?

You don't connect to Witnesses, you connect to servers running the witness_node executable, such as wss://bitshares.openledger.info/ws. If you're serious about this mobile wallet you should probably provide such an API server yourself. If on the other hand you want to pay for that service you could probably find someone to do it for you..
Worker: dev.bitsharesblocks

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
right, but many more mobile wallets will be released after ours I'm sure.
 
how hard would it be to get the Witnesses to offer this level of service. i could code it so that the mobile wallets send a flag to the Witnesses saying "hey, i'm a mobile device, please filter out the big shit so my data plan isn't exhausted!" thoughts..?
 
let's encourage some other devs to make mobile wallets too...
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat

Offline kenCode

  • Hero Member
  • *****
  • Posts: 2283
    • View Profile
    • Agorise
We got the connection to Blocktrades working tonight so that now all POS systems can also accept Bitcoin, Litecoin, Dogecoin, Dash and the other top cryptos. This weekend will be doing a lot of UI cleanup. Will get the eReceipts and QR codes going next week and begin the customer/shopper screens:
https://www.youtube.com/watch?v=uHOYG408ohg&list=PLjbx3qSmDe7RYkRMIEuFyYyG7_vvKgou0&index=6
kenCode - Decentraliser @ Agorise
Matrix/Keybase/Hive/Commun/Github: @Agorise
www.PalmPay.chat