Qortal Project

The future of blockchain platforms

User Tools

Site Tools

Trace:
qort_hosting_-_previous_model_on_qora

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
Next revisionBoth sides next revision
qort_hosting_-_previous_model_on_qora [08/14/2020 01:54] – created croweticqort_hosting_-_previous_model_on_qora [09/10/2020 07:54] – gfactor
Line 1: Line 1:
 ====QORA Hosting Model==== ====QORA Hosting Model====
- 
-==The original QORA model== 
- 
    
-⊕ QORA had a model that was based on uploading data to the chain itself ⊕ +QORA had a model that was based on uploading data to the chain itself. In order to place data upon the QORA hosting, a user would have to register a name to use as a 'domain name' within QORA, then, utilizing transactions, upload data TO THE CHAIN. This data then was referenced by the registername, and was able to pull up HTML/js hosted within the blockchain.
- +
-In order to place data upon the QORA hosting, a user would have to register a name to use as a 'domain name' within QORA, then, utilizing transactions, upload data TO THE CHAIN. This data then was referenced by the registername, and was able to pull up HTML/js hosted within the blockchain.+
  
-===Example of QORA hosted site===+===Example of QORA Hosted Site===
  
 Here...by 'bouncing' through a hosted QORA node, you can see an image hosted on the QORA chain... [[http://node6.qora.org:9090/qortal]]  Here...by 'bouncing' through a hosted QORA node, you can see an image hosted on the QORA chain... [[http://node6.qora.org:9090/qortal]] 
Line 20: Line 15:
 \\ \\
  
-====QORA Hosting model 'issues'====+====QORA Hosting Model 'Issues'====
  
 \\ \\
  
-Now, at first glance, one may say 'wow, that's incredible!', which is partially true... However, when getting down to the details and problems that are faced by using this model, one may see why Qortal decided to do away with it in favor of another method of data storage.+Now, at first glance, one may say 'wow, that's incredible!', which is partially true, however, when getting down to the details and problems that are faced by using this model, one may see why Qortal decided to do away with it in favor of another method of data storage.
  
 \\ \\
  
-===issue#1 - bloating the chain===+===Issue #1 - Bloating The Chain===
  
 \\ \\
Line 40: Line 35:
 The bloat, is the main issue that Qortal didn't use the on-chain storage model. The bloat, is the main issue that Qortal didn't use the on-chain storage model.
  
-===Issue#2 - Data uploads in transactions (of a limited size, and lack of proper coding for data uploads)===+===Issue #2 - Data uploads in transactions (of a limited size, and lack of proper coding for data uploads)===
  
 QORA's upload feature, was both coded incorrectly, and limited in multiple ways... For one, the coding of the upload, didn't make use of more than ONE transaction... Therefore if users needed more data than one block could hold (which isn't a lot, and is basically assured to be not enough data for a full site of any real use...) the user would have to manually structure multiple transactions with the max data in each, ensuring that the data didn't exceed the single block limit, and take their time and effort to ensure each upload fulfilled the previous upload's data to the point of being usable. QORA's upload feature, was both coded incorrectly, and limited in multiple ways... For one, the coding of the upload, didn't make use of more than ONE transaction... Therefore if users needed more data than one block could hold (which isn't a lot, and is basically assured to be not enough data for a full site of any real use...) the user would have to manually structure multiple transactions with the max data in each, ensuring that the data didn't exceed the single block limit, and take their time and effort to ensure each upload fulfilled the previous upload's data to the point of being usable.
Line 46: Line 41:
 \\ \\
  
-This caused all kinds of issues for users, when they attempted to upload too much data for a single tx, got an error, and assumed that websites could only be the size of a single tx... which wasn't the case.+This caused all kinds of issues for users, when they attempted to upload too much data for a single tx, got an error, and assumed that websites could only be the size of a single tx which wasn't the case.
  
 \\ \\

Page Tools