Versions Compared

Old Version 14

changes.mady.by.user Medha Parlikar

Saved on

compared with

New Version 15

changes.mady.by.user Medha Parlikar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


RequirementDescriptionPriorityNotesStatus
1Retrieve data asynchronouslyAs a mobile app developer, I need to send all my request asynchronously, so that my apps are fast.Must Have
  • The RSong demo requests the song, song metadata and song artwork asynchronously.  It's not clear to Medha if this is a hard requirement.  There isn't any reason why the song can't be requested first, followed by the metadata.

2Monitor Requests for DataAs a validator, I need to know how much of my node's resources are spent on data access requests so that I can set the prices for transactions properly.Must Have
  • There has to be a dashboard that shows how many requests for data the node is servicing.  
  • There should also be a dashboard that shows how much data is being returned in these requests. This metric can be in aggregate if needed.

3PerformanceIn principle, A dApp developer will want to provide a user a transaction receipt with at least the same speed at which the transaction itself is processed.  Must Have
  • This means that half of the transaction processing time is in fact, in the retrieval of the transaction confirmation. 

4Deployment ID

Each deployment has a userid and timestamp, userid is generated randomly for (public key associated with private key used to sign transaction ) for that particular deployment by the client software.  These keys should be looked up in the block store.

Must Have
  • Users need a way to retrieve transaction receipts for their deployments.

...