Sounds good to me. Keith <div>On 7/15/07, Jussi Kukkonen <<a href="mailto:jhkukkon@cc.hut.fi">jhkukkon@cc.hut.fi</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> 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: <a href="http://gitweb.freedesktop.org/?p=geoclue.git;a=commit;h=82a304331a6bd6ba438de5a73a3d968189447018"> http://gitweb.freedesktop.org/?p=geoclue.git;a=commit;h=82a304331a6bd6ba438de5a73a3d968189447018</a> 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 <a href="mailto:GeoClue@lists.freedesktop.org">GeoClue@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/geoclue">http://lists.freedesktop.org/mailman/listinfo/geoclue</a> </blockquote></div>