"Peter Marek" <[EMAIL PROTECTED]> " wrote on 09/28/2007 07:36:33
AM:
>
> I have some basic issue understanding how SAF HPI API
> functions (like the FUMI stuff you added) translates to
> plugin abi calls & functions.
>
> is there any documentation or info that could help to
> create more understanding ? Or is it simply teh case that
> the FUMI API is ready but the plugin ABI is not FUMi
> ready ? Same applies to DIMI.
>
Both the HPI API and plugin ABI are FUMI ready as of 2.10. However, there
are no plugins in OpenHPI that implement the FUMI plugin ABIs (or DIMI),
yet.
include/oh_handler.h lists all of the plugin ABIs and has comments
indicating to which HPI API it corresponds.
All FUMI APIs (and DIMI) are passed down to the plugin. The difference is
that the SessionId is replaced with the plugin's handler as the first
param..
Also, the library performs a series of checks on the parameters before
passing it down to the plugin. In general, these are:
- Session check
- Resource check (existence and capabilities)
- RDR check (existence of FUMI num)
There are other checks that are performed depending on the API. Not all
checks required by the spec are pratical for the core library to do. These
checks are left up to the plugin (e.g. checking for the existence of FUMI
BankNum and/or DIMI TestNum). The best thing is to look at src/safhpi.c to
know exactly what the library is doing for the API in question (its pretty
readable) before it gets to the plugin.
--Renier-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
