Yeah Twitter is working just fine but it is HTTP. (I've done a Twitter client as well and got no problems) The example has no authentication because Twitter doesn't need an authentication for the public timeline. (I know the example)
The HTTPS approach should work like the normal HTTP thing but I don't get it working. :( And even more disappointing I don't know why. I went through a lot of mailing list even for the apache 4 alpha (android uses a lot of classes from the apache 4 libs) but haven't found anything. So I have to assume that this is a bug. On 21 Jul., 21:54, "Mark Murphy" <[EMAIL PROTECTED]> wrote: > > Could someone tell me what I have to change in here? > > A Google search for: > > android twitter client > > turned up: > > http://sleepydroid.blogspot.com/2008/06/consuming-xml-from-twitter.html > > In there, the author is not using HTTP Authentication nor an https:// URL. > > I've never written to Twitter API, so I have no way of validating whether > that code works or not, but it's at least another source of information > for you. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ -- Available Now! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
