The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
I have an application that is written in c# (exe) - which would need to communicate with another windows applications (possibly written in c++ / c#). I could have easily exposed api or any other methods. But then the third party application insists I use Hid.
given that, I have few choices and would like to ask what would be the best design choice here:
implement a KMDF Virtual Hid driver. This driver would be a relay in-between the my application and the other application. My application will send a command to the driver and driver will relay it back to the other application. I would use input report for one way and output reports for other way. but this design looks not very good.
I guess I couldn't get away with just writing a umdf based simple hid mini driver of some sort and use that as a relay.
typical flow would be something like
Application A -> ask the driver what is the state of the device
driver then send this to a raw PDO in VHF
Application B -> will be always reading PDO and if it finds anything there, will send a report to the driver
drive will then send this back to the Application A
my question is : what is your opinion on this relay mechanism and what could i do to improve this design?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Writing WDF Drivers||7 Dec 2020||LIVE ONLINE|
|Internals & Software Drivers||25 Jan 2021||LIVE ONLINE|
|Developing Minifilters||8 March 2021||LIVE ONLINE|