Results 1 to 2 of 2

Thread: IL 1.1.2 Content pipe Read API

  1. #1
    Junior Member
    Join Date
    Jan 2010
    Posts
    6

    IL 1.1.2 Content pipe Read API

    Is there any particular reason that the Read API is defined without a mean to return the number of bytes actually read?

    CPresult (*Read)(
    CPhandle hContent,
    CPbyte *pData,
    CPuint nSize);

    This makes API not being able to support partial read while using user supplied buffer, I would propose a trivial revision to,

    CPresult (*Read)(
    CPhandle hContent,
    CPbyte *pData,
    CPuint * nSize);

    Similar to that of ReadBuffer, can any one comment on this?

    Regards,

    /MG

  2. #2
    Junior Member
    Join Date
    Jan 2010
    Posts
    6

    Re: IL 1.1.2 Content pipe Read API

    The similar is true to the Write API.

    One thing I can think of is 'slight' performance hit (by internally in the API updating the byte count), but the benefit seems well override the incompleteness of API, since without being able to support partial reading/writing, it leaves API quite not usable when considering retrieving data at the end of content, or writing with multiple attempts.

    Thanks,

    /MG

Similar Threads

  1. Clarification on Content Pipe Implementation
    By andrewcoopergarmin in forum OpenMAX AL
    Replies: 2
    Last Post: 09-18-2012, 06:32 AM
  2. IL 1.1.2 Content pipe CheckAvailableBytes API
    By mgao in forum OpenMAX IL
    Replies: 0
    Last Post: 01-28-2011, 10:42 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •