The current implementation of the Twitter adaptor, used in the demo, has the
annoying property that one sees Tweets way too burstily. I can imagine an app
developer wanting smoother/faster delivery - so the adaptor should support a
QoS parameter that can cause partial frames to flow when data is coming too
slowly. (In real life scenarios this may be less of an issue, but who knows.)
This seems like it would apply to any source of data that might sometimes be a
trickle and other times be a flood - during trickle times, you may not want to
wait for frames to fill. This is therefore a general feature request and not a
request about the Twitter adaptor specifics - the solution should be in the
infrastructure, vs. being in the adaptors themselves.
Original issue reported on code.google.com by dtab...@gmail.com on 20 Apr 2013 at 3:26
Original issue reported on code.google.com by
dtab...@gmail.com
on 20 Apr 2013 at 3:26