XML from API broken?

0 views
Skip to first unread message

thilo

unread,
Oct 13, 2007, 5:11:47 AM10/13/07
to Twitter Development Talk
It seems the XML returned from the API is broken sometimes, e.g.
curl http://twitter.com/statuses/friends_timeline/kosmar.xml
returns garbage at the end. May be its only wrong for long XML output
as other screen_names work fine.

Sat Oct 13 11:09:20 CEST 2007:
--snip
<status>
<created_at>Fri Oct 12 20:05:52 +0000 2007</created_at>
<id>331549822</id>
<text>fahren fahrradweg und verkehrsinseln. w&#228;hrend der folge
heroes gef&#252;hlte 23 meter vorw&#228;rts gekommen. kriege lust auf
kaiserschmarn #a3</text>
<source>web</source>
<truncated>false</truncated>
<user>
<id>894471</id>
<name>dotdean</name>
<screen_name>dotdean</screen_name>
<location>cologne, germany</location>
<description>male 1980 apple web2.0 blogger flickr socialmedia</
description>
<profile_image_url>http://s3.amazonaws.com/twitter_production/
profile_images/26985392/av-14848_normal.png</profile_image_url>
<url>http://www.pl0g.de</url>
<protected>false</protected>
</user>
</status>
<status>
<created_at>Fri Oct 12 20:05:07 +0000 2007</created_at>
<id>331548192</id>
<text>Latest News Getting Doc North of the Border: Doc Searls on
the PlanetEye Board: Just caught.. http://tinyurl.com/yuk89d</text>
<source>&lt;a href="http://twitterfeed.com"&gt;??|p,?
Y???????$??Y??
OO??|?Y?(a?*?????????<N??4?L??*?\y???ح*?X???L4??5??\p|?????*??FB???L8@?
=????isġis???<??k???P??(c<zl??
????
KY9
?j ???`?????????,??4x? ?j ????`T???x?????????????LTx??SC

--snip

thilo

unread,
Oct 14, 2007, 10:56:53 AM10/14/07
to Twitter Development Talk
just a comment to my previous post: To reproduce the error click on
http://twitter.com/statuses/friends_timeline/kosmar.xml twice one
after another


Alex Payne

unread,
Oct 18, 2007, 7:00:07 PM10/18/07
to twitter-deve...@googlegroups.com
This is likely due to some cache corruption on our end. I'll look into it.


--
Alex Payne
http://twitter.com/al3x

thilo

unread,
Oct 19, 2007, 9:36:38 AM10/19/07
to Twitter Development Talk
thank you Alex. As far as I can tell it works fine now. However, the
XML output from the API is still much more outdated than the json (cf.
my other post on the list).

On Oct 19, 1:00 am, "Alex Payne" <a...@al3x.net> wrote:
> This is likely due to some cache corruption on our end. I'll look into it.
>

dclinton...@gmail.com

unread,
Nov 27, 2007, 11:35:31 AM11/27/07
to Twitter Development Talk
I am still seeing this kind of cache corruption on a fairly regular
basis, especially using the http://twitter.com/statuses/friends.xml
call.

I am also seeing a problem where when I request the friends list for a
give user (using the id param) I receive back the list for a different
user. My application is a Twitter aggregator which makes calls for
lots of different users. My theory is that you are creating a hash
based on the source IP and URL so when there is a hash collision I get
the wrong response.

Doug

On Oct 18, 11:00 pm, "Alex Payne" <a...@al3x.net> wrote:
> This is likely due to somecachecorruptionon our end. I'll look into it.

Alex Payne

unread,
Nov 27, 2007, 8:14:43 PM11/27/07
to twitter-deve...@googlegroups.com
That's not the basis for the hashes we use. The cache corruption
seems to be network issues inside our cage. We're working with our
hosting provider to remedy it.

Reply all
Reply to author
Forward
0 new messages