I/O Port Pattern
-
I am working in a Program that works with 3 serial ports 1 I/O Board and a Camera. Anyone know about some design pattern made to Asynchronusly read the information on all these devices?
JO :)
-
Ju@ncho wrote:
know about some design pattern made to Asynchronusly read the information on all these devices?
I don't know about design patterns but the Windows API includes Overlapped IO features, is that what you mean?
No, what i am meaning is a way to encapsulate the Overlapped IO features of serial ports plus other custom overlapped IO features of other devices (ie Adquisitions Boards)in a single design pattern. I think that the observer pattern should work but i am not sure..
JO :)
-
No, what i am meaning is a way to encapsulate the Overlapped IO features of serial ports plus other custom overlapped IO features of other devices (ie Adquisitions Boards)in a single design pattern. I think that the observer pattern should work but i am not sure..
JO :)
Ju@ncho wrote:
the Overlapped IO features of serial ports plus other custom overlapped IO features of other devices (ie Adquisitions Boards)
Ok. I know what Overlapped IO is, I know what Asynchronous is, I have no idea what "IO features of serial ports" or "custom overlapped IO features of Adquisitions Boards" are.
Ju@ncho wrote:
I think that the observer pattern should work but i am not sure..
Well the observer pattern has two sides (observable - observer) where the observer side supports multiplicity. So far you have only discussed the observable side of your scenario so we have no way of knowing if that pattern exists in your problem space. Also I have no idea how or why the "features" you referred to are related to the observer pattern.
-
Ju@ncho wrote:
the Overlapped IO features of serial ports plus other custom overlapped IO features of other devices (ie Adquisitions Boards)
Ok. I know what Overlapped IO is, I know what Asynchronous is, I have no idea what "IO features of serial ports" or "custom overlapped IO features of Adquisitions Boards" are.
Ju@ncho wrote:
I think that the observer pattern should work but i am not sure..
Well the observer pattern has two sides (observable - observer) where the observer side supports multiplicity. So far you have only discussed the observable side of your scenario so we have no way of knowing if that pattern exists in your problem space. Also I have no idea how or why the "features" you referred to are related to the observer pattern.
may be you can have a look at Microsoft's Asyncronous block from MS patterns and practices. not sure. cheers varun.y.sharma@gmail.com