Re: [RFC] BlueZ D-Bus Sim Access Profile Server API description

[Suraj Sumangala <suraj@Atheros.com>]

Hi,
On 9/13/2010 10:17 PM, Johan Hedberg wrote:

> Why would you want to expose these extra SAP profile details to the
> Agent? The bluetoothd side should take care of all details like this
> whenever possible. The only relevant data that needs to be transmitted
> from the Agent to bluetoothd in this case is the ATR and bluetoothd can
> then proceed with creating a proper SAP response packet based on that.
>
>> How do we map the D-Bus error return to the ResultCode?
>
> You'd need to define some sort of mapping table yourself. The list of
> possible result codes is quite short (8 in SAP 1.1) so this shouldn't be
> too hard. E.g. "Error, card not accessible" (0x02) could map to the
> D-Bus error org.bluez.SapError.CardNotAccessible.

The idea was to return the ResultCode as a string from the agent and map 
it to the corresponding code in the server.

If we can define error codes for each result, that would be fine.
>
> Johan

Regards
Suraj