Bump!
If someone hasn't tackled this issue by then, I'll work on it after I get
back from ZendCon in a few weeks. Seems like an easy patch.
On Sat, Sep 6, 2008 at 12:14 PM, Derek Gathright <[EMAIL PROTECTED]> wrote:
> Looks like this is how it works.
>
> JSON output
> [{"test":"data"}]
>
> JSON with Padding (JSONP) output
> <?= $_GET['callback'] ?>([{"test":"data"}]);
> Once Laconi.ca supports JSONP, it can open the door to 100% javascript
> clients. Thoughts?
>
>
> On Sat, Sep 6, 2008 at 11:57 AM, Derek Gathright <[EMAIL PROTECTED]> wrote:
>
>> Hmm... well I'm reading up on the JSONP response format, and it appears
>> that the response given is slightly different from the standard JSON format.
>> So is the answer that Laconi.ca's Twitter API doesn't yet support JSONP?
>> If so, anyone wanna shed some light on how we make that happen? Will look
>> into it more myself.
>> http://bob.pythonmac.org/archives/2005/12/05/remote-json-jsonp/
>>
>>
>> On Sat, Sep 6, 2008 at 11:48 AM, Derek Gathright <[EMAIL PROTECTED]>wrote:
>>
>>> I'm having an issue with the Identi.ca JSON feeds in JQuery. It works
>>> perfect when pulling from the Twitter feed, but after the call, JQuery fails
>>> to take action with the response when calling the Identi.ca equivalent.
>>>
>>> Here's a snippet to demonstrate how one works and the other doesn't
>>>
>>> <html>
>>> <head>
>>> <script type="text/javascript" src="
>>> http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.js";></script>
>>> <script>
>>> $(document).ready(function() {
>>> //var url = 'http://twitter.com/statuses/friends_timeline.json';
>>> var url = 'http://identi.ca/api/statuses/friends_timeline.json';
>>> $.ajax({
>>> type : "GET",
>>> url : url,
>>> dataType : "jsonp",
>>> success : function(data)
>>> {
>>> alert("success");
>>> },
>>> error : function(){
>>> alert("error");
>>> }
>>> });
>>> });
>>> </script>
>>> </head>
>>> </html>
>>>
>>>
>>> Was thinking it might have to do with something in the headers. From my
>>> experience with JQuery, anytime it fails to take action after an AJAX call,
>>> it received the wrong data type. But, this doesn't give me any clues
>>> either.
>>>
>>> http://identi.ca/api/statuses/public_timeline.json
>>> ======
>>> HTTP/1.1 200 OK
>>> Date: Sat, 06 Sep 2008 16:36:26 GMT
>>> Server: Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.3 with Suhosin-Patch
>>> X-Powered-By: PHP/5.2.4-2ubuntu5.3
>>> Transfer-Encoding: chunked
>>> Content-Type: application/json; charset=utf-8
>>> ======
>>>
>>>
>>> http://twitter.com/statuses/public_timeline.json
>>> ======
>>> HTTP/1.1 200 OK
>>> Date: Sat, 06 Sep 2008 16:35:42 GMT
>>> Server: hi
>>> Content-Encoding: UTF-8
>>> Content-Type: application/json;charset=utf-8
>>> Content-Length: 11783
>>> Cache-Control: max-age=300
>>> Expires: Sat, 06 Sep 2008 16:40:44 GMT
>>> Connection: close
>>> ======
>>>
>>>
>>> Any ideas?
>>>
>>
>>
>
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
