feat(cu): Handle READ Messages

[twilson63]

Problem

The AO Spec a message may have a tag Read-Only and if set to "True", then the cu should evaluate the message and return a result, but not save any state changes. Implementing this message in the CU as a parallel worker request and can be run on a separate worker.

See https://hackmd.io/P4bCcgsmTpKpuN-nSE54ng#Messages29

[ppedziwiatr]

Out of curiosity - how does this differ from dry-runs? https://github.com/permaweb/ao/tree/main/connect#dryrun

[twilson63]

dry-runs are external calls a READ is a message that can be submit from an AO process, to read data from another AO Process ``` Send({Target = WAR, ["READ-ONLY"] = "True", Action = "Balance", Recipient = ao.id }) ```

…

On Tue, Jul 30, 2024 at 11:25 AM just_ppe ***@***.***> wrote: Out of curiosity - how does this differ from dry-runs? https://github.com/permaweb/ao/tree/main/connect#dryrun — Reply to this email directly, view it on GitHub <#927 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAFGLA5KQNQIBJFYF7ZYYTZO6V77AVCNFSM6AAAAABLWIUFQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJYGYZDKMJYGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>