We have a real-time API and we're not afraid to use it. Are you?

#1

Post by wulczer » Mon, Oct 31, 2011, 4:42 PM UTC

We have a real-time API and we're not afraid to use it. Are you?
ducksboard.com

Re: We have a real-time API and we're not afraid to use it. Are you?

#2

Post by wulczer » Mon, Oct 31, 2011, 5:08 PM UTC

If you have any questions, I'll be here all day ;)

Re: We have a real-time API and we're not afraid to use it. Are you?

#3

Post by rwolf » Mon, Oct 31, 2011, 5:38 PM UTC

After poking around little bit, it appears you need to poll for updates. To clarify, when you say "real-time" you mean "changes are reflected quickly" and not "changes are pushed to clients"?

Re: We have a real-time API and we're not afraid to use it. Are you?

#4

Post by wulczer » Mon, Oct 31, 2011, 5:41 PM UTC

rwolf wrote: post #3

After poking around little bit, it appears you need to poll for updates. To clarify, when you say "real-time" you mean "changes are reflected quickly" and not "changes are pushed to clients"?

Nope, we push changes to clients.

The exact workflow is: the initial data is pulled over HTTP, the code connects to our server over WebSockets and after that no more requests are made. The real-time updates are pushed over the WebSocket connection.

Re: We have a real-time API and we're not afraid to use it. Are you?

#5

Post by Swizec » Mon, Oct 31, 2011, 5:42 PM UTC

I think I want to have some fun with this. No idea whatsoever what I want to build, but it might be totally awesome.

Re: We have a real-time API and we're not afraid to use it. Are you?

#6

Post by rwolf » Mon, Oct 31, 2011, 5:44 PM UTC

wulczer wrote: post #4

rwolf wrote: post #3

After poking around little bit, it appears you need to poll for updates. To clarify, when you say "real-time" you mean "changes are reflected quickly" and not "changes are pushed to clients"?

Nope, we push changes to clients. The exact workflow is: the initial data is pulled over HTTP, the code connects to our server over WebSockets and after that no more requests are made. The real-time updates are pushed over the WebSocket connection.

Thanks for clarifying. I'm not sure how I missed that when reviewing the example code.

Re: We have a real-time API and we're not afraid to use it. Are you?

#7

Post by joshu » Mon, Oct 31, 2011, 5:54 PM UTC

Anyone have any thoughts on how to do the display side of this in VERY low power? Are there cheap android tablets or whatever that might be suitable?

I want to do something like this but don't need to consume tons of watts...

Re: We have a real-time API and we're not afraid to use it. Are you?

#8

Post by wulczer » Mon, Oct 31, 2011, 5:59 PM UTC

joshu wrote: post #7

Anyone have any thoughts on how to do the display side of this in VERY low power? Are there cheap android tablets or whatever that might be suitable? I want to do something like this but don't need to consume tons of watts...

We have plans to make an interface that's less bling-heavy and more power-friendly, but it won't hit production anytime soon.

Another way is to simply write your own visualisation. If you're interested in getting early-alpha-unstable-omg access to the read APIs (HTTP and WebSockets), shoot us an email to hello@ducksboard.com

Re: We have a real-time API and we're not afraid to use it. Are you?

#9

Post by asmosoinio » Mon, Oct 31, 2011, 6:00 PM UTC

Do you have a story for the name? The first thing I thought of was "duck duck go is going real-time?".

Re: We have a real-time API and we're not afraid to use it. Are you?

#10

Post by nickbarnwell » Mon, Oct 31, 2011, 6:03 PM UTC

Excited to test it out with Podio. Will save me writing my own dashboard interface and make customers pretty happy in the process