Announcement

Collapse
No announcement yet.

Proposed Web Service: Simple Online/Offline Status

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

  • Proposed Web Service: Simple Online/Offline Status

    This web service would determine if the client hardware was online, or offline. This would be useful in cases where you want to do live things like turn on/off stuff via the FB where the web service that controls that needs to know if the machine is online or not.

    There should probably be a single method that would be consumed by the client and one for other web services to use.

    Method exposed to client:

    Code:
    KeepAlive(string user, string passhash)
    Method exposed to other web clients:

    Code:
    ClientStatus(string user)
    In REST it would return something like:

    Code:
    <xml> <status>offline</status> </xml>
    The idea is the client calls KeepAlive every 5-10mins or so and the service keeps tabs on how long since the last "ping". If the KeepAlive "ping" hasn't been fired in a certain timeframe, the client status is updated internally to "offline".
    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.

  • #2
    Good idea. Are there other services such as GPS information that should be included in some sort of base service that the user can control.

    For example, a gps service that could be turned on and off by the user and would be able to be queried by another service or app that is not in the car? Perhaps other things such as the app that is being run and the screen the user is on?

    I'm just thinking aloud here. Not sure if these make sense or not but I was aiming towards trying to give other services the ability to understand your context - say, if you've been sitting still for more than 3 or 4 minutes, a traffic service might look for congestion information or traffic cameras nearby.

    The traffic service doesn't need to query your car for the information. It could query some type of status service like this one and it would either get access or be denied access depending on user controlled settings.
    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


    • #3
      Originally posted by Bugbyte View Post
      Good idea. Are there other services such as GPS information that should be included in some sort of base service that the user can control.
      I think simple car status info should all be rolled into this web sevice. Here is some sample info that could be used by other webservices/web front-ends...
      • Computer Status - on/off (if off, the rest of the follow values should be switched to null)
      • Current GPS Location
      • Engine Status (on/off)
      • Current FE Status - somewhat like auto twitter (listening to MP3, watching DVD, etc...)

      A short list that may be useful for other webservices or web front-ends is what I see this being used for.

      Comment


      • #4
        Car engine status, gps location, and speed would probably be best used in other services. Those services would also likely use this service. For example, when you upload traffic information, the Traffic service could call KeepAlive so that the entire web service collection knows that you're online.

        We could lump the traffic and tracking service into this, but I would keep the KeepAlive method available as the lowest common denominator (user may want online/offline status, but not tracking, and not traffic, etc).
        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


        • #5
          Agreed.....users are typically very cautious when it comes to tracking so that needs to be separate from any of the basic services.

          Engine On/Off should probably be part of the obd statistics service

          Current FE status should probably stay though...how bout this instead:
          KeepAlive(string user, string passhash, string status)

          That way it can be a simple Online/Offline status or if the user wants it can be a detailed message (playing xyz, navigating to abc, etc.). As long as it defaults to offline after x minutes without a ping it should still work just as well.
          openMobile - An open source C# Front End (why choose openMobile?)
          - Always Recruiting Developers -
          Like what you see? Donations are always welcome

          Comment


          • #6
            Current FE status should probably stay though...how bout this instead:
            KeepAlive(string user, string passhash, string status)
            That works. We may even want to take it one step further and make it:

            Code:
            KeepAlive(string user, string passhash, string frontend, string status
            Where frontend would be something like "RevFE 0.43" or "OpenMobile 0.99".
            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

            Working...
            X