[Standards] Simple Jingle example(s) and spec(s) wanted

[Remko Tronçon]

> People who implemented XEP-0117 and did the old file transfer... if
> there's a new one, are they still 'Intermediate IM Client'

Regardless of whether or not the combination of Jingle-FT and S5B is a
good idea, the fact still remains that the only protocol to implement
voice in XMPP is Jingle. I have been wanting to implement the Jingle
signaling code for a long time, but i can't even get that far because
there is way too much to do in a first step: hardware interaction,
voice streaming implementation, implementation of complex protocols to
transport the streams, and *then* the signaling code . I'm pretty sure
other people feel the same way as well. This is why I want a file
transfer profile of Jingle: so that I can completely focus on the
signaling code without worrying about anything else (which is already
a complex state protocol in itself), and have that tested in a first
step. Then we can start focus on all the dirty stuff like transports
and media hardware interaction.

Personally, I think the current spec is nice, works from time to time
and from implementation to implementation, but then again, i'm overall
disappointed in its performance.  All I want is something that works,
and let's face it, the only guys that came up with that so far are
Google. Since they are definitely interested in interoperability with
other clients (libjingle), I'm pretty sure they seriously considered
using the current spec, but found it inadequate. What's even better,
besides going through the effort of creating a library on the side to
help interoperate with their protocol, they are willing to put effort
in cooperating to make an improved standard which, although similar to
what they have right now, still requires an additional effort from
their side to implement and comply to as well.

Personally, I don't mind implementing both specs in a client. If the
step from a protocol for voice (which we need as well) to a protocol
for file transfer is minimal, and if the file transfer protocol makes
it easier to implement the voice signaling and firewall traversal (and
even voice) step-wise, then why not use it? A client just starting up
would only have to implement one protocol, and have it extended to
have capabilities like voice, video, ... It would already clean up a
few XEPs from the 'long' XEP list.

cheers,
Remko