Re: Simple Arbitrary Data Exchange

--===============0453553987==
Content-Type: multipart/alternative; boundary="000000000000fc870805934e63d2"

--000000000000fc870805934e63d2
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 24 Sep 2019 at 09:30, Kevin Smith <[email protected]> wrote:

> On 24 Sep 2019, at 09:20, Dave Cridland <[email protected]> wrote:
> >
> > Is there interest amongst the developer community to provide a
> generalised, interoperable facility for the exchange of simple, arbitrary
> data between consenting entities? I'm calling this SADEX, but I'm really,
> really, not wed to this name.
> >
> > The key here would be the API - you'd want to provide the equivalent of
> a function call such as:
> >
> > void sadex_message(JID to, String type, String data)
> >
> > You'd also need a callback for when you receive some, and perhaps an IQ
> form.
>
> It=E2=80=99d depend how wed you are to exactly what you describe there. S=
wiften=E2=80=99s
> API would make more sense to do message->setSadexType(=E2=80=A6) and
> message->setSadexData(), and a callback wouldn=E2=80=99t make much sense,=
 you=E2=80=99d
> just message->getSadexType and message->getSadexData() (or maybe
> message->getSadex()->(get|set)(Data|Type)(). Not what you describe, but
> still equivalent to how subject/body work in the API, and I don=E2=80=99t=
 see a
> problem with adding it.
>

I think we're looking at a type (something morally equivalent to an XML
namespace) and payload, and we want to ensure both are set or neither.

But you're absolutely right that whatever API is used should fit the
existing APIs of the library.

But ultimately, I'm most interested in a low-friction way of exchanging
application-specific data that will guide people away from doing worse
things. The constraints here would seem to be "easy to use", "obvious", and
probably "in the core/default download".

Dave.

--000000000000fc870805934e63d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, 24 Sep 2019 at 09:30, Kevin S=
mith &lt;<a href=3D"mailto:[email protected]">[email protected]</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2=
4 Sep 2019, at 09:20, Dave Cridland &lt;<a href=3D"mailto:[email protected]=
" target=3D"_blank">[email protected]</a>&gt; wrote:<br>
&gt; <br>
&gt; Is there interest amongst the developer community to provide a general=
ised, interoperable facility for the exchange of simple, arbitrary data bet=
ween consenting entities? I&#39;m calling this SADEX, but I&#39;m really, r=
eally, not wed to this name.<br>
&gt; <br>
&gt; The key here would be the API - you&#39;d want to provide the equivale=
nt of a function call such as:<br>
&gt; <br>
&gt; void sadex_message(JID to, String type, String data)<br>
&gt; <br>
&gt; You&#39;d also need a callback for when you receive some, and perhaps =
an IQ form.<br>
<br>
It=E2=80=99d depend how wed you are to exactly what you describe there. Swi=
ften=E2=80=99s API would make more sense to do message-&gt;setSadexType(=E2=
=80=A6) and message-&gt;setSadexData(), and a callback wouldn=E2=80=99t mak=
e much sense, you=E2=80=99d just message-&gt;getSadexType and message-&gt;g=
etSadexData() (or maybe message-&gt;getSadex()-&gt;(get|set)(Data|Type)(). =
Not what you describe, but still equivalent to how subject/body work in the=
 API, and I don=E2=80=99t see a problem with adding it.<br></blockquote><di=
v><br></div><div>I think we&#39;re looking at a type (something morally equ=
ivalent to an XML namespace) and payload, and we want to ensure both are se=
t or neither.</div><div><br></div><div>But you&#39;re absolutely right that=
 whatever API is used should fit the existing APIs of the library.</div><di=
v><br></div><div>But ultimately, I&#39;m most interested in a low-friction =
way of exchanging application-specific data that will guide people away fro=
m doing worse things. The constraints here would seem to be &quot;easy to u=
se&quot;, &quot;obvious&quot;, and probably &quot;in the core/default downl=
oad&quot;.</div><div><br></div><div>Dave.=C2=A0</div></div></div>

--000000000000fc870805934e63d2--

--===============0453553987==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
JDev mailing list
Info: https://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: [email protected]
_______________________________________________

--===============0453553987==--