backend error handling

[keith preston]

Sounds good to me.

Keith

On 7/15/07, Jussi Kukkonen <jhkukkon at cc.hut.fi> wrote:
>
> Jussi Kukkonen wrote:
> > I'd like to implement some error handling for the position backends. I'm
> > pretty new to GError, so comments are welcome. I'm thinking different
> > backend types are different "error domains", and this is my view on how
> > it should look (using position backend/"error domain" as example):
>
> As there were no objections, I pushed the changes to fd.o git:
>
> http://gitweb.freedesktop.org/?p=geoclue.git;a=commit;h=82a304331a6bd6ba438de5a73a3d968189447018
>
> The errors and error codes are defined in
> backend/geoclue_position_error.[ch]. Currently the list of error codes
> for position backends looks like this:
>
>   GEOCLUE_POSITION_ERROR_NOSERVICE,
>      /* Backend cannot connect to needed service */
>
>   GEOCLUE_POSITION_ERROR_MALFORMEDDATA,
>      /* Received data, but it is unreadable */
>
>   GEOCLUE_POSITION_ERROR_NODATA,
>      /* Used service cannot provide position data at this time*/
>
>   GEOCLUE_POSITION_ERROR_NOTSUPPORTED,
>      /* Backend does not implement this method */
>
>   GEOCLUE_POSITION_ERROR_FAILED
>      /* generic fatal error */
>
> --jussi
>
>
>
> _______________________________________________
> GeoClue mailing list
> GeoClue at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/geoclue
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/geoclue/attachments/20070716/89145e24/attachment.html