|
From: Vadim P. <vpe...@ho...> - 2005-06-28 19:34:02
|
I read through your HW Emulator list. It is pretty old, but here is some = feedback anyway: Simulating reader protocols is a very time consuming task. I have done = not for most readers, but I could justify it because I need to test = device drivers. Documentation for reader protocols usually comes with = the readers and one cannot download it from HW vendor web site. This = really means that creating and maintaining HW simulators will require = buying reader or probably requesting a loaner from manufacturer. If purpose of creating HW emulator is to test middleware, I would opt = for creating a simple protocol and use it for simulation.=20 As far as RAReader interface is concerned, it is a pretty good shot. = However there are a few things to consider: * Readers have 1-N antennas and some configuration attributes are = related to antennas. setReaderProperties() can only deal with device = configuration, but not antenna configuration. One solution is to have = Antenna[] getAntennas() and setAntennaProperties( Antenna ant ) * Status notification is a well-defined function can be represented = through a listener interface, without Savant EMS messaging.Status = notification is needed to for monitoring purpose, for other application = entities to react to status (e.g. a workflow that handles a production = line, etc.), or to initiate device recovery process. All of these = aspects can be encapsulated in a framework and exposed through facade = interfaces. Thanks. |