While you'll find most applications on handsets communicate with api.twitter.com, search.twitter.com, and twitter.com directly -- there are likely a handful of applications that communicate with a proxy server of some kind as an intermediary between the device and Twitter.
If they're talking directly to Twitter though, they'll be doing so through HTTP. @episod <http://twitter.com/episod> - Taylor Singletary On Wed, Apr 20, 2011 at 12:35 PM, sunderjs <sunde...@gmail.com> wrote: > Hello, > > I'm working on implementing mobile data plans for social networking > sites including Twitter. Requirement is to identify Twitter traffic > from mobile devices and charge distinctively from other data packets. > Since there are different ways that Twitter can be accessed from a > mobile device (browser, client app, embedded links etc), i would like > to know the possible patterns that i should identify. Clients using > standard Twitter APIs would be RESTful and generating HTTP traffic > eventually. Question is does the prepackaged client apps (such as HTC > Sense, SE Timescape, Moto Blur, Samsung Social Hub etc ) also use > public Twitter APIs ? Or is it a different arrangement altogether. > > thanks > Sunderjeet > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk