Deprecation Notice: XML Support on Streaming APIs will be dropped on Dec 6th, 2010

13,094 views
Skip to first unread message

Taylor Singletary

unread,
Nov 8, 2010, 5:21:54 PM11/8/10
to twitter-development-talk, twitter-api-announce
Hi Developers,

We will end support for XML on all Streaming APIs on Dec 6th, 2010, after encouraging developers to use JSON-based output formats for some time now. This deprecation does not apply to the REST or Search APIs, but all clients requesting XML from stream.twitter.com, regardless of role and method (sample, filter, follow, etc) will be affected.

If you're currently connecting to an XML-based Twitter Streaming API endpoint, you'll need to migrate your code to consume JSON by Monday December 6th, 2010 (approximately four weeks from now). According to our records, only a very small number of developers are consuming XML via streams today. 

Now would be a good time for streaming clients to verify that they are using JSON. If you're still using XML, please migrate to JSON as soon as possible. User/Site Streams implementations should already be JSON-only.

As a reminder, we encourage using OAuth to connect to the Streaming API -- basic authentication, while supported today on stream.twitter.com, will also be deprecated at a future date. 

Please respond with any questions or concerns.

Thanks!
Taylor Singletary

M. Edward (Ed) Borasky

unread,
Nov 8, 2010, 5:45:11 PM11/8/10
to twitter-deve...@googlegroups.com, Taylor Singletary, twitter-development-talk, twitter-api-announce
Hooray!!!

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos


Quoting Taylor Singletary <taylorsi...@twitter.com>:

> --
> 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
>

Reply all
Reply to author
Forward
0 new messages