elective-stereophonic
elective-stereophonic
Multipart Messages Standard
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Author Topic: Multipart Messages Standard  (Read 2071 times)

kushti

  • Core Dev
  • Sr. Member
  • ****
  • Karma: +184/-5
  • Offline Offline
  • Posts: 384
  • Nxt Core & Apps Dev
    • View Profile
Multipart Messages Standard
« on: October 13, 2014, 10:46:21 am »

I think it's better to have standard for multipart messages to make block explorers implementation simpler. There are probably two options for it:
  • Use referencedTransactionFullHash field to link a message with previous in a chain
  • Some code usage in message contents, e.g. starting it with "---$prevTransactionId---" 

I think first option is usually better, though referencing could be used for other purposes and block explorers need to make additional checks.
Logged
for donations / messages: NXT-PKXM-WH25-UXXG-CJAVD (alias: kushti)

Jean-Luc

  • Core Dev
  • Hero Member
  • *****
  • Karma: +816/-81
  • Offline Offline
  • Posts: 1610
    • View Profile
Re: Multipart Messages Standard
« Reply #1 on: October 13, 2014, 11:09:20 am »

First we should consider increasing the allowed message length (up to the maximum that would fit in a block, allowing a single transaction to occupy the whole block), and simply charge more for longer messages. It will still be more efficient and take less space than splitting the message in multiple transactions, and the fee based on length will overall be lower than paying for several transactions.

If still not enough, the difference between chaining messages using referenced transactions and any other way is that only the referenced transactions method guarantees that preceding parts of the message are in the blockchain (although it can't guarantee that all expected future parts will be included too). But there is also the limitation of referenced transactions chain length not exceeding 10 transactions total.

Logged
GPG key fingerprint: 263A 9EB0 29CF C77A 3D06  FD13 811D 6940 E1E4 240C
NXT-X4LF-9A4G-WN9Z-2R322

kushti

  • Core Dev
  • Sr. Member
  • ****
  • Karma: +184/-5
  • Offline Offline
  • Posts: 384
  • Nxt Core & Apps Dev
    • View Profile
Re: Multipart Messages Standard
« Reply #2 on: October 13, 2014, 11:40:08 pm »

1. In the first place, I meant industry standard for apps devs not core improvements
2. Message size limit should be lifted for sure. Even 5K could be considered as much more suitable for applications.
3. 10 transactions could be ok probably in most cases(btw how it's enforced in NRS code?)
Logged
for donations / messages: NXT-PKXM-WH25-UXXG-CJAVD (alias: kushti)
 

elective-stereophonic
elective-stereophonic
assembly
assembly