--===============1622568699==
Content-Type: multipart/signed;
  boundary="nextPart2910079.5du3lxZITa";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2910079.5du3lxZITa
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

=46riedrich W. H. Kossebau wrote:
>The protocol is a custom one, so I thought I just use QDataStream on
>QTCPSocket everywhere. But how will this work if the data doesn't come
> as fast over the network as the other side reads it, so the buffer is
> underrun? (Or is this no problem, does QDataStream just wait? I found
> no hint to a Timeout, which would be nice to have, then). The Qt
> examples do not seem to use QDataStream that way, too.

QDataStream wants the entire datastream block before you start reading. If=
=20
you are *sure* you received everything that QDataStream wrote, you can=20
use it. That's usually done by placing a size marker at the beginning of=20
the data, before the datastream itself.

Otherwise, I'd recommend just using raw data. Don't use QDataStream.

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart2910079.5du3lxZITa
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBI00a5M/XwBW70U1gRAlaVAKCvO8PFS6zIoiIQ9ZUyK+NczKlENwCgnR9c
646H2D7nnuT80cqY1TgXiYo=
=Pdso
-----END PGP SIGNATURE-----

--nextPart2910079.5du3lxZITa--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1622568699==--