# Basic Real-Time Server Data Questions (Digg's ARC)

**URL:** <https://forum.kirupa.com/t/basic-real-time-server-data-questions-diggs-arc/266055>\
**Category:** flash\
**Created:** [July 15, 2008, 9:07pm UTC](https://forum.kirupa.com/t/basic-real-time-server-data-questions-diggs-arc/266055 "2008-07-15T21:07:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pittsburghjoe](https://avatars.discourse-cdn.com/v4/letter/p/e19adc/32.png) [@pittsburghjoe](https://forum.kirupa.com/u/pittsburghjoe)\
**Post date:** [July 15, 2008, 9:07pm UTC](https://forum.kirupa.com/t/basic-real-time-server-data-questions-diggs-arc/266055/1 "2008-07-15T21:07:42Z")

</div>

[http://labs.digg.com/arc/](http://labs.digg.com/arc/)

I’m guessing that it’s using the digg Flash api  
[http://code.google.com/p/diggflashdevkit/](http://code.google.com/p/diggflashdevkit/)

But I’m not advanced enough to know what’s really going on.  
Here goes:

1. Is [digg.com](http://digg.com) constantly sending out new data to feed any swf’s that might have the api baked in Or is your local swf constantly requesting new data through the api?
2. Is digg’s api considered a web service?
3. Is digg using something like Adobe LiveCycle Data Services (LCDS) or BlazeDS?

And for the bonus question:  
Is there anything wrong with sending multiple requests to a webservice to get real-time data?

EDIT:for those that found this thread:  
from: [http://apidoc.digg.com/BasicConcepts](http://apidoc.digg.com/BasicConcepts)  
“Now consider an application that keeps track of current data in real time. That application should:  
[LIST=1]  
[_]Make an initial request with no min\_date or max\_date argument. The response will include only the latest items. The end of the implicit time period can be found in the timestamp property of the root element of the response–it’ll be close to the time when the request was received.  
[_]Note the _timestamp_ in the response, and make another request with that timestamp as the _min\_date_ argument. The response will include items which immediately follow that timestamp, and a new value in the _timestamp_ property.  
[\*]Repeat step 2 to get even more current data.  
[/LIST]  
But remember, [#BePolitePlease|be polite]: Don’t make requests every second, or our operations guys may see your application as an attacking robit. Consider making one request per minute, and processing or displaying the data between requests. That’s how Stamen’s flash toolkit does its magic.”