B. Petersen a043557c44 move payload to {payload:PAYLOAD} to allow additional parameters ...

additional parameters will be `summary` and `msg` (for an info-message)
right now, and maybe more in the future (`aggregated`, `fast`, `to` ...),
so adding just more parameters easily gets wild.

also, this makes adaptions easier as no ffi needs to be adapted
when we add more parameters.

finally, sending is in-sync with receiving, database and wire now,
one receives similar objects as one sends,
which also looks like the right thing :)

for now, `sendUpdate()` also allows to use the old, unwrapped payload
to not immediately break existing `.xdc`, however, that will be removed soon,
probably before the first release.

2022-01-15 00:10:59 +01:00

..

aeap-mvp.rst

Update aeap-mvp.rst

2021-11-25 16:18:30 +01:00

group-sync.rst

fix link

2020-11-16 11:47:48 +01:00

msgwork_new_imap_jobs.rst

add a draft for how to simplify and replace imap-jobs handling

2020-07-15 11:23:23 +02:00

webxdc-dev-reference.md

move payload to {payload:PAYLOAD} to allow additional parameters

2022-01-15 00:10:59 +01:00