[prev in list] [next in list] [prev in thread] [next in thread] 

List:       libusb-devel
Subject:    Re: [Libusb-devel] Make async libusb API backend specific?
From:       Orin Eman <orin.eman () gmail ! com>
Date:       2010-01-29 21:49:11
Message-ID: 25b306ec1001291349o78499ae8ked58dae3af26842e () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Fri, Jan 29, 2010 at 12:41 PM, Peter Stuge <peter@stuge.se> wrote:

> Orin Eman wrote:
> > > we need to hear how actual developers out there would prefer us
> > > to handle async on Windows
> >
> > In a nutshell, the same way WinUSB does it, which is pretty much
> > the same as regular overlapped IO on Windows.
>
> In that case, libusb would not offer a portable API. The API would
> differ depending on which platform the program is built for, thus
> pushing an extra portability issue onto the application - when in
> fact that's something we would like to solve within libusb.
>
> It would be nice to avoid it - but maybe it's just not possible?
>


 Actually, the libusb async API is quite similar to Windows overlapped IO
already and should work fine under Windows.  I don't think a Windows
programmer is going to find it much different to use than the WinUSB
interface.



>
> And there is of course a point in offering familiar APIs and
> workflows for each platform.
>

Indeed.  I don't think a Windows programmer is going to be messing with
poll() to be sure.

Orin.

[Attachment #5 (text/html)]

<div class="gmail_quote">On Fri, Jan 29, 2010 at 12:41 PM, Peter Stuge <span \
dir="ltr">&lt;<a href="mailto:peter@stuge.se">peter@stuge.se</a>&gt;</span> \
wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px \
0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Orin Eman wrote:<br>&gt; &gt; we need to hear \
how actual developers out there would prefer us<br>&gt; &gt; to handle async on \
Windows<br> &gt;<br>&gt; In a nutshell, the same way WinUSB does it, which is pretty \
much<br>&gt; the same as regular overlapped IO on Windows.<br><br>In that case, \
libusb would not offer a portable API. The API would<br>differ depending on which \
platform the program is built for, thus<br> pushing an extra portability issue onto \
the application - when in<br>fact that&#39;s something we would like to solve within \
libusb.<br><br>It would be nice to avoid it - but maybe it&#39;s just not \
possible?<br></blockquote>

<div> </div>
<div> </div>
<div>
<div>Actually, the libusb async API is quite similar to Windows overlapped IO already \
and should work fine under Windows.  I don&#39;t think a Windows programmer is going \
to find it much different to use than the WinUSB interface.</div>

<div> </div>
<div> </div></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; \
BORDER-LEFT: #ccc 1px solid"><br>And there is of course a point in offering familiar \
APIs and<br>workflows for each platform.<br></blockquote>

<div> </div>
<div>Indeed.  I don&#39;t think a Windows programmer is going to be messing with \
poll() to be sure.</div> <div> </div>
<div>Orin.</div>
<div> </div>
<div> </div></div>



------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com

_______________________________________________
Libusb-devel mailing list
Libusb-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-devel


[prev in list] [next in list] [prev in thread] [next in thread]