[Interest] QCanBusDevice inheritance

Thiago Macieira thiago.macieira at intel.com
Wed Sep 9 17:14:23 CEST 2015

On Wednesday 09 September 2015 13:18:33 Blasche Alexander wrote:
> The QIODevice architecture was not a good fit for CAN bus. The API must
> enable the user to interpret the various frames received on the bus. In
> addition to the payload, each frame may come from different sources, has
> different types and other attributes. This means that the API requires at
> least an abstraction on frame level. For each new frame that you send you
> may adjust the frame attributes as well.

You're describing QUdpDatagram (https://codereview.qt-project.org/108336), 
which is being added to QUdpSocket.

> After all you don't set a new IP for each UDP datagram. 

You can do it. You don't have to, but you can.

That said, the send/receive datagram functionality bypasses the regular 
QIODevice virtuals and goes straight to the socket engine.
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

More information about the Interest mailing list