When "talking" to a server, which route would be the best?

May 23, 2012 at 5:40 PM

I am wanting to integrate a synchronize tool, among other items, and would like some input on which type of technology we should use.

We can go really 1 of two routes:

  1. node server with websockets (constant connection open as long as UI is running and on turntable.fm)
  2. Doing generic POST requests to a server

The main question is whether or not we need to have a constant socket open with the client at all times when we will probably only being sending requests every couple of minutes, or longer.


What do you think?

May 23, 2012 at 5:42 PM

What kind of information is going to be synchronized?

May 23, 2012 at 5:46 PM

Well, first & foremost, I would like to sync settings/preferences. I, for one, use Turntable.fm on multiple computers, so it would be nice to save my display type and favorited users on my pm list. 

May 23, 2012 at 5:47 PM

If syncing preferences, using a single HTTP/S request would be most efficient and stable, however later when pulling data from things like TTStats or syncing data between multiple clients, node would be the way to go.

May 23, 2012 at 6:18 PM

I think so too. I think for ease of simplicity, we should just do a HTTP request, but switch over to node later on, what do you think?

May 23, 2012 at 7:43 PM

Works for now. We'll program keeping that in mind.