Announcement

Collapse
No announcement yet.

Proposed Webservice - Error Reporting

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Proposed Webservice - Error Reporting

    Error reporting by clients needs to be handled in a secure and structured way. It should not matter what OS/FE, a single webservice should be sufficient for everyone.

    The question is, what exactly do we report, how much info, and what to classify by? Do we log OS errors, FE only errors, or something else? Do we limit to only webservices (they could log here as well), apps that call webservices, or the entire FE, or what?

    Also, we would need to decide what info gets saved, but thats dependant upon what we want to log.

    I am opening this up for discussion....

  • #2
    I think it should only be used by the web services. Our database would fill rather quickly if we logged OS events and I can't think of how FE errors would be very useful to the user or to OSDash devs unless those errors originate from the OSDash client implementation. In which case, it should be used for only OSDash related errors.
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

    Comment


    • #3
      I concur. Things like an improper call to the web service, loss of data or connection, stuff like that should be logged.

      FE errors only to the extent that the FE generates the web service error.
      Originally posted by ghettocruzer
      I was gung ho on building a PC [until] just recently. However, between my new phone having internet and GPS and all...and this kit...Im starting to have trouble justfiying it haha.
      Want to:
      -Find out about the new iBug iPad install?
      -Find out about carPC's in just 5 minutes? View the Car PC 101 video

      Comment


      • #4
        I think webservice related errors should be logged at the server level not by a "web service" since they should never occur. Connection errors, well, no need to even log those there kinda expected with the connections most people will be using. This service is a great idea if its used for FE errors (or in the case of linuxICE even OS level errors), just store a string thats up to the FE dev as to what it contains. This would make a great debugging tool!!
        openMobile - An open source C# Front End (why choose openMobile?)
        - Always Recruiting Developers -
        Like what you see? Donations are always welcome

        Comment


        • #5
          Originally posted by justchat_1 View Post
          I think webservice related errors should be logged at the server level not by a "web service" since they should never occur. Connection errors, well, no need to even log those there kinda expected with the connections most people will be using. This service is a great idea if its used for FE errors (or in the case of linuxICE even OS level errors), just store a string thats up to the FE dev as to what it contains. This would make a great debugging tool!!
          I concur.... this would be a great tool for FE devs. You cannot rely on the general public to do correct error and bug reporting. We could log if plugins didnt load correctly, if songs are missing, if certain files are not working, or anything else.

          The webservices are so simple that errors should not occur. If a service fails, its more likely the server is down or the connection is down, and thus webservice calls are *impossible*.

          Comment

          Working...
          X