We'll mail again and post on the @twitterapi account before we cry havoc and let slip the hounds.
-John On Jul 11, 2:26 pm, Joel Strellner <j...@twitturly.com> wrote: > John, > > Any chance you can allow us to send an additional variable when we > connect and you guys send it in the new format? This would allow for > overlap and testing. > > -Joel > > On Jul 11, 2009, at 7:04 AM, John Kalucki <jkalu...@gmail.com> wrote: > > > > > Laurent, > > > There are examples of the new objects on the Streaming API wiki. The > > XML and JSON formats are, sadly, not orthogonal. The objects aren't > > flowing to give developers time to adjust. We'll probably enable this > > in the middle of next week. > > > -John > > > On Jul 11, 12:34 am, Laurent Eschenauer <laurent.eschena...@gmail.com> > > wrote: > >> Hi John, > > >> I can't find such thing as a status or delete object in the JSON > >> feed. > >> There is indeed a <status> enveloppe in the XML, but the > >> corresponding > >> JSON object seems to be already one level deeper, only encapsulating > >> the data from the status itself. > > >> Could you please clarify what we should be expecting to see in JSON ? > >> And maybe also provide some sample objects in the Wiki, both for XML > >> and JSON ? > > >> Thanks ! > > >> -Laurent > > >> On Jul 10, 8:00 pm, John Kalucki <jkalu...@gmail.com> wrote: > > >>> Note: The Streaming API is currently under a limited alpha test, > >>> details below. > > >>> Please test that your Streaming API clients can handle unexpected > >>> objects in the markup stream. Status deletion notice support is > >>> being > >>> added, but will be disabled until at least Thursday July 16th to > >>> allow > >>> developers a chance to check their code. From the > >>> wiki,http://apiwiki.twitter.com/Streaming-API-Documentation: > > >>> Streams may also contain status deletion notices. Clients are > >>> urged to > >>> honor deletion requests and discard deleted statuses immediately. > > >>> * XML: <delete><status><id>1234</id><user_id>3</user_id></ > >>> status></delete> > >>> * JSON: { "delete": { "status": { "id": 1234, "user_id": 3 } } } > > >>> Objects other than <status> and <delete> may be introduced into the > >>> markup stream in a future release. Please ensure that your parser is > >>> tolerant of unexpected objects. > > >>> Important Alpha Test Note: > >>> The Streaming API (aka Hosebird) is currently under an alpha test. > >>> All > >>> developers using the Streaming API must tolerate possible > >>> unannounced > >>> and extended periods of unavailability, especially during off-hours, > >>> Pacific Time. New features, resources and policies are being > >>> deployed > >>> on very little, if any, notice. Any developer may experiment with > >>> the > >>> unrestricted resources and provide feedback via this list. Access to > >>> restricted resources is extremely limited and is only granted on a > >>> case-by-case basis after acceptance of an additional terms of > >>> service > >>> document. > > >>> -John Kalucki > >>> twitter.com/jkalucki > >>> Services, Twitter Inc.
