Create - IO

[alyhxn]

@todo

#19

• Create - IO
  • Implement base
  • Integrate into components
  • Use standard communication methods given components may reside in different machines.
  • Finalize
  • @output ❓ IO_v0.0.?
    • next Refactor - playproject #19

[alyhxn]

Tasks - 2025.05.12

• Update - IO_v0.0.?
  • @input 📦 task-messenger-io
  • Combined sk and pk for nodes to use just pid. - 10min
  • Feedback proceessing - 7h
  • Setup - 1h
  • Logged tasks - 10min
  • @output 📦 IO_v0.0.1

Worklog

worklog-266

[alyhxn]

Tasks - 2025.05.18

• Update - IO_v0.0.1
  • Experimentation with net prop - 3h
  • Discussion - 7h
  • @output 📦 IO_v0.0.2

---

Worklog

worklog-267

[alyhxn]

Tasks - 2025-05-19

• Update - IO_v0.0.1
  • Implemented the proposed net with a real example - 3h
  • Added io.md and net.md - 10min
  • Debugging - 1h
  • Logged tasks - 5min
  • @output 📦 IO_v0.0.2

---

Worklog

worklog-268

---

Proposals

1. Find a way to remove msg_cache from modules.

[serapath]

feedback 2025.05.19

problem

As far as i understand, the way this is now working is:

1. the page module defines an override and
2. instructres the button module to inform
3. the page module with a register message when a click occurs
4. using some data provided by the fallback, e.g. rainbow_theme

This seems problematic.

This defines specific events that are supposed to be emitted.
But the net property should only define who connects to whom and nothing else.

I am not saying the solution is trival to code when using the io module, but we can modify the io module to support the features we need once we know what we want.

Maybe a connecting port needs to initially send a message to define in what api calls or event there is interested in and those are either emitted by sending them at runtime or they are triggered because the fallback/override net property defined the connections?

The important part is to store these subscribe/unsubscribe events or connect/disconnect events in the database, so we can properly restore all connections when the page reloads!

---

OTHER PROBLEMS (WITH SOLUTION SHOWN IN SCREENSHOT)

The button is just a button and as such doesn't know rainbow_theme

Also, the fallback/override runs only initially, but what if at runtime at some point the button should send something else than rainbow_theme, maybe dark_theme. How does this work then?

Additionally, in the button on every click event, we then have generic code to cycle through possible messages on every click to potentially send a message and as you noticed you said you are already looking for a way to avoid msg_cache object.

And finally on every button click, a new connection is initialized via io.at, even though once a connection is established it can be used to send many messages.

---

Another example

Here the page defines the button should send a specific event to page.

Instead we should build a solution based on page just simply connecting to the button
Now we need to think, if this connection will be auto-initialized, then both trigger:

// page.js
io.on(port => {
  if (port.to === button_address) { ... }
})

and

// btn.js
io.on(port => {
  if (port.to === page_address) { ... }
})

Now thinking of these code snippets, the btn was written not knowing where it will be used, so **how can it know what to do when a port is from a specific address? How does it know this address wants to subscribe to "click" events? ...maybe thats easy because maybe a button literally offers no other service, but lets say there was also click and hold or double click events...

Next, how does page know, once it receives a port with a button address, what to expect from it? ...

---

Some further thoughts about a solution given a scenario:

1. Y1 and Y2: The button module doesnt know the theme, it only gets clicked.
2. X: The theme selection module probably has all themes stored in its internal sdb.drive
3. Z: the app module is the only thing deveXloped by the app developer so he can set overides
4. W: Actually also the app developer controls the page to apply theme i suppose.

So if X already uses a button dependency Y1 internally and listens to its clicks to send a theme to page to all theme listeners. Then Z or W can register as theme listeners.

But also we want to add Y2 to trigger X

X subscribes to Y1 click event by default

We want to override to make X subsribe to Y2 too or even instead.

[alyhxn]

Tasks - 2025.05.31

• Update - IO_v0.0.3
  • Update the net property - 1h30min
  • @output 📦 IO_v0.0.4

---

Worklog

worklog-272

[serapath]

feedback 2025.06.01

page reload compatible io api

first issue, function connect () {} is not supposed or allowed to return anything. The reasoning is:

1. if a component loads after a page reload, all existing connections can be restored by calling the "on(port => {})callback, while a port that was stored in a variable after a call toconst port = at(...)` is not restorable
2. the idea of at() is to indicate to which address to connect or maybe disconnect, basically later on, calling at(address) with the same address means stop connecting (not disconnecting), which means, if for whatever reason, a connection gets disrupted, the system will automatically try to re-connect later on which will trigger a new on(port => {}) call and the at() calls will only add and remove to the persistable set of addresses etc... that we currently want to establish and re-stablish connections until we disconnect on purpose and say that we no longer want to connect.

This code is not needed or should not be needed.
Basically, just like .watch(onbatch) triggers for all the file changes in the drive, io.on(port => {}) triggers for all the connections and calling at(address1) and later at(address1) is supposed to trigger adding and/or removing a specific address from the Set of addresses we want to establish connections to.

It also means, that if a connection breaks/disconnects but the address is still in the Set, it will automatically reconncet and trigger io.on(port => {}) again.

I know - this wasn't really yet so explicitly mentioned, but can you refactor and keep that in mind and if you see problems with it, lets discuss

So if in your component, you want to manually maintain an object const connections = {} you can populate it inside the io.on(port => connections[port.to] = port) callback function.

---

net for "sending" data/args -> sender/receiver

This is correct. The data for message (e.g. events) does not always come from the user. it might depend on the component state and some data received earlier via network or even the user, but when the page loads initially or later reloads, there is some sort of data user in event handlers, like in your example the swtch event uses those args:[...]

The general idea is

1. there is an address and type field.
2. any data associated depends on the type so maybe we can interpret types in the context of io/net as input types

I guess we can keep this for now, but later on, they too should represent "type named" datasets, so each type of message or event has its state that can be used to process a message of that type :-)

But... i guess for now we can just think of it like that and refactor/change things later on when we try to consolidate api's to make it smoother and more convenient to use :-) ...same with your button.onclick handler - quite verbose with many checks and even a parse/stringify etc... all correct, but also a candidate to make it smoother/simpler later on, but i would recommend lets just make io feature complete and stable before we discuss simplifications :-)

Please add this description or concept to the documentation of io/net so we wont forget :-)

---