2015-09-10 9:49 GMT+02:00 Blasche Alexander
:
>
>>> Another inefficiency of the QIODevice approach would be that each frame
> Hi,
>
>>> would have to be serialized to a QByteArray on the user API side just to be
>> >unserialized on the backend side again. I have yet to see a backend API that
>> >do
>> Another inefficiency of the QIODevice approach would be that each frame
Hi,
>> would have to be serialized to a QByteArray on the user API side just to be
> >unserialized on the backend side again. I have yet to see a backend API that
> >doesn't deal with a frame based API. There is simply not
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
2015-09-09 15:18 GMT+02:00 Blasche Alexander
:
> Hi,
>
>
>>Thanks for your response but I still don't get why QIODevice has been
>>discarded for CAN while it is used for QUdpSocket.
>
>>First, frames can always be divided into bytes, there length is an
>>integer multiple of byte. If you are talking
Hi,
>Thanks for your response but I still don't get why QIODevice has been
>discarded for CAN while it is used for QUdpSocket.
>First, frames can always be divided into bytes, there length is an
>integer multiple of byte. If you are talking about the fact that
>fields within a frame are not 8 bi
Hi,
>Thanks for your response but I still don't get why QIODevice has been
>discarded for CAN while it is used for QUdpSocket.
>First, frames can always be divided into bytes, there length is an
>integer multiple of byte. If you are talking about the fact that
>fields within a frame are not 8 bi
Benjamin,
I forwarded your message to the mailing list back (you likely forgot to do
it?). Now it could available to comments and for other developers (if you
don't object).
BR,
Denis
2015-09-09 15:46 GMT+03:00 Denis Shienkov :
> Benjamin,
>
> I forwarded your message to the mailing list back (
Hi.
Because QIODevice is inconsistent with the CAN frames. The CAN uses a
minimal entity - frame, which can not be divided to bytes. Besides,
QIODevice's read/write/bytesAvailable methods has not sense, you can not
read/write a half of frame and so on. You can not know a size of frame
to seria
