I have created a Fire Eagle application which is an web-auth application

named CCTLocBlog.

But I met problems when I am tring the php walk through examples which

in the Fire Eagle Documents.

I have finished setting up the background like upload the fireeagle.php

and OAuth.php to a sub directry in my server, and the php version on my

server is 5.2.6.

After all this done, I followed the guide and created the walkthru.php

and insert my own Consumer key and secret, but when I access it though

my browser FireFox, it appears nothing, all blank, not even a notice

or warning...

What is going on? Is there any problem in my php programming? Or is

this possiblly my server issue?

Thank you if you leave your advices.

Sorry, I should have said that I was in need of international weather;
or at least European.

Thanks.

dorzey

--- In fireeagle@yahoogroups.com, aymanshamma <no_reply@...> wrote:
>
> Hi Dorzey,
>
> The Y!API for weather allows you to pass a postal code:
>
> http://weather.yahooapis.com/forecastrss?p=94089
>
> which will work if you only need weather inside the USA.
>
> Do you need international weather?
>
> -ayman.
>
>
> --- In fireeagle@yahoogroups.com, "paulsdoran" <dorzey@> wrote:
> >
> > Hello,
> >
> > I've just started to play around with the Fire Eagle API.  I wish to
> > use my current location to get a weather forecast for where I am from
> > Yahoo! Weather.  However, Yahoo! Weather uses 'Location ID' in its
> > request URL (http://developer.yahoo.com/weather/).
> >
> > I can't find any documentation on how to combine Fire Eagle and Yahoo!
> > Weather.  I'm aware that the Mac wdiget
> > (http://widgets.fireeagle.yahoo.net/) does what I want; I just want to
> > know how it did it.
> >
> > Hope someone can help. Thanks.
> >
> > dorzey
> >
>

I was just testing Fire Eagle with the latest (trunk) OAuth Java
library code:

    http://code.google.com/p/oauth

The latest build of OAuth Java relies on HTTP's "100 (Continue)
status" feature.  This feature is described in RFC 2616 section 8.2.3:

    http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html

My application sends an HTTP POST request with this header:

    Expect: 100-Continue

Yahoo Fire Eagle responds with:

    HTTP/1.1 411 Length Required

Is this a bug in Fire Eagle or was this intentional?  Does Fire Eagle
lack support for "Expect: 100-Continue" requests?


Sean



Request
=======

[DEBUG] headers - >> POST /api/0.1/update HTTP/1.1
[DEBUG] headers - >> Content-Type: application/x-www-form-urlencoded
[DEBUG] headers - >> Transfer-Encoding: chunked
[DEBUG] headers - >> Host: fireeagle.yahooapis.com
[DEBUG] headers - >> Connection: Keep-Alive
[DEBUG] headers - >> User-Agent: Apache-HttpClient/4.0-beta1 (java 1.4)
[DEBUG] headers - >> Expect: 100-Continue

Response
========

[DEBUG] wire - << "HTTP/1.1 411 Length Required[EOL]"
[DEBUG] wire - << "Date: Tue, 04 Nov 2008 19:10:49 GMT[EOL]"
[DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
STA POL HEA PRE GOV"[EOL]"
[DEBUG] wire - << "Cache-Control: private[EOL]"
[DEBUG] wire - << "Connection: close[EOL]"
[DEBUG] wire - << "Transfer-Encoding: chunked[EOL]"
[DEBUG] wire - << "Content-Type: text/html; charset=iso-8859-1[EOL]"
[DEBUG] headers - << HTTP/1.1 411 Length Required
[DEBUG] headers - << Date: Tue, 04 Nov 2008 19:10:49 GMT
[DEBUG] headers - << P3P:
policyref="http://p3p.yahoo.com/w3c/p3p.xml", CP="CAO DSP COR CUR ADM
DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR DELi SAMi OTRi UNRi PUBi
IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA POL HEA PRE GOV"
[DEBUG] headers - << Cache-Control: private
[DEBUG] headers - << Connection: close
[DEBUG] headers - << Transfer-Encoding: chunked
[DEBUG] headers - << Content-Type: text/html; charset=iso-8859-1

I have a mobile application that sends requests to Fire Eagle. I'd
like to use gzip compression to reduce the amount of data transferred.
This technique is described in Yahoo's article on HTTP performance:

   http://developer.yahoo.com/performance/rules.html

My application includes the Accept-Encoding header in the
HTTP request:

    Accept-Encoding: gzip

Fire Eagle seems to ignore the Accept-Encoding header.  The Fire Eagle
response is not compressed.

Is the Fire Eagle team planning to support gzip compression?

Sean


HTTP request
============

[DEBUG] headers - >> GET
/api/0.1/lookup?address=200%20SW%20Main%20St%2C%20Portland%20Oregon&oauth_token=\
fAyISyDVIfcQ&oauth_consumer_key=aCk6Ghm7cUSI&oauth_signature_method=HMAC-SHA1&oa\
uth_timestamp=1225922777&oauth_nonce=1225922777407395000&oauth_version=1.0&oauth\
_signature=tZsGDG8wMWAVyXaXjNlhxZTtq5U%3D
HTTP/1.1
[DEBUG] headers - >> Host: fireeagle.yahooapis.com
[DEBUG] headers - >> Connection: Keep-Alive
[DEBUG] headers - >> User-Agent: Apache-HttpClient/4.0-beta1 (java 1.4)
[DEBUG] headers - >> Cookie:
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDbcoG4DXMAgZIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--26e79f656fd00d5\
8ff2093eda8f86eb908abaf18
[DEBUG] headers - >> Cookie2: $Version=1
[DEBUG] headers - >> Accept-Encoding: gzip


HTTP response
=============

[DEBUG] wire - << "Status: 200 OK[EOL]"
[DEBUG] wire - << "X-Runtime: 0.10327[EOL]"
[DEBUG] wire - << "ETag: "b0a0d6324db250eba1b25ce2c16f476e"[EOL]"
[DEBUG] wire - << "X-XRDS-Location:
http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
[DEBUG] wire - << "Cache-Control: private, max-age=0,
must-revalidate[EOL]"
[DEBUG] wire - << "Content-Length: 422[EOL]"
[DEBUG] wire - << "X-Cache: MISS from web4.bh.sp1.yahoo.net[EOL]"
[DEBUG] wire - << "Connection: close[EOL]"
[DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
[DEBUG] wire - << "<rsp stat="ok">[\n]"
[DEBUG] wire - << "
<query>address=200%20SW%20Main%20St,%20Portland%20Oregon</query>[\n]"
[DEBUG] wire - << "  <locations count="1" start="0" total="1">[\n]"
[DEBUG] wire - << "    <location>[\n]"
[DEBUG] wire - << "      <name>200 SW Main St, Portland, OR</name>[\n]"
[DEBUG] wire - << "      <normal-name>97204</normal-name>[\n]"
[DEBUG] wire - << "      <place-id
exact-match="false">M6sX7NOYA5uuZBoySA</place-id>[\n]"
[DEBUG] wire - << "      <woeid exact-match="false">12798505</woeid>[\n]"
[DEBUG] wire - << "    </location>[\n]"
[DEBUG] wire - << "  </locations>[\n]"
[DEBUG] wire - << "</rsp>[\n]"

On Tue, Nov 4, 2008 at 21:32, jfireeagle <sean@...> wrote:
>
> I was just testing Fire Eagle with the latest (trunk) OAuth Java
> library code:
>
> http://code.google.com/p/oauth
>
> The latest build of OAuth Java relies on HTTP's "100 (Continue)
> status" feature. This feature is described in RFC 2616 section 8.2.3:
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
>
> My application sends an HTTP POST request with this header:
>
> Expect: 100-Continue
>
> Yahoo Fire Eagle responds with:
>
> HTTP/1.1 411 Length Required

Which seems reasonable -- my reading is that you send *all* headers
and then wait for the 100 - continue response before sending the
request body.  Your client didn't send a content-lenth in the headers
and the server just informs you that it wants to see that.

   Holger

> I was just testing Fire Eagle with the latest (trunk) OAuth Java
> library code:
>
> http://code.google.com/p/oauth
>
> The latest build of OAuth Java relies on HTTP's "100 (Continue)
> status" feature. This feature is described in RFC 2616 section 8.2.3:
>
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
>
> My application sends an HTTP POST request with this header:
>
> Expect: 100-Continue
>
> Yahoo Fire Eagle responds with:
>
> HTTP/1.1 411 Length Required
>
> Is this a bug in Fire Eagle or was this intentional? Does Fire Eagle
> lack support for "Expect: 100-Continue" requests?

It should support them by virtue of running a standards-compliant web
server (i.e. it's not an app-level concern).

I'm guessing that Holger is correct.  If you want to resume
disconnected requests, it's important for the server end to know how
much data was going to be sent in order to resume properly.

If you continue to have problems after checking the order of the
headers you're sending, write back to the list and I'll spend some
more time investigating.

seth

> I have a mobile application that sends requests to Fire Eagle. I'd
> like to use gzip compression to reduce the amount of data transferred.
> This technique is described in Yahoo's article on HTTP performance:
>
> http://developer.yahoo.com/performance/rules.html
>
> My application includes the Accept-Encoding header in the
> HTTP request:
>
> Accept-Encoding: gzip
>
> Fire Eagle seems to ignore the Accept-Encoding header. The Fire Eagle
> response is not compressed.
>
> Is the Fire Eagle team planning to support gzip compression?

We already do (YSlow will confirm this for you).  However, you may need to send:
Accept-Encoding: gzip, deflate

seth

> We already do (YSlow will confirm this for you).  However, you
> may need to send:
>
> Accept-Encoding: gzip, deflate
>
> seth

I sent a request to Fire Eagle a few moments ago.  The request uses
the "Accept-Encoding: gzip, deflate" header.

Fire Eagle's response did not have a "Content-Encoding: gzip" header.

Can you tell me if there is something wrong with my request?


Request
=======

[DEBUG] wire - >> "GET
/api/0.1/user?oauth_token=gvPAzDEbd2gh&oauth_consumer_key=aCk6Ghm7cUSI&oauth_sig\
nature_method=HMAC-SHA1&oauth_timestamp=1226096451&oauth_nonce=12260964514094510\
00&oauth_version=1.0&oauth_signature=3m0SDzL%2BGaM0TZ8%2BWvqJDqQx5KM%3D
HTTP/1.1[EOL]"
[DEBUG] wire - >> "Host: fireeagle.yahooapis.com[EOL]"
[DEBUG] wire - >> "Connection: Keep-Alive[EOL]"
[DEBUG] wire - >> "User-Agent: Apache-HttpClient/4.0-beta1 (java
1.4)[EOL]"
[DEBUG] wire - >> "Cookie:
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4Cgmy5TIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5d8668423e17a97\
9e865a9641aea93ce63a6f64a[EOL]"
[DEBUG] wire - >> "Cookie2: $Version=1[EOL]"
[DEBUG] wire - >> "Accept-Encoding: gzip, deflate[EOL]"
[DEBUG] wire - >> "[EOL]"


Response
========

[DEBUG] wire - << "HTTP/1.1 200 OK[EOL]"
[DEBUG] wire - << "Date: Fri, 07 Nov 2008 22:20:51 GMT[EOL]"
[DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
STA POL HEA PRE GOV"[EOL]"
[DEBUG] wire - << "Content-Type: application/xml; charset=utf-8[EOL]"
[DEBUG] wire - << "Set-Cookie:
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4D0mTpTIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--858ca7c87d1eec8\
20b4a39e8eacd6cdeabd3279b;
path=/[EOL]"
[DEBUG] wire - << "Status: 200 OK[EOL]"
[DEBUG] wire - << "X-Runtime: 0.12992[EOL]"
[DEBUG] wire - << "ETag: "7537e3e2654bf4c8ede462c2e6e7160e"[EOL]"
[DEBUG] wire - << "X-XRDS-Location:
http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
[DEBUG] wire - << "Cache-Control: private, max-age=0,
must-revalidate[EOL]"
[DEBUG] wire - << "Content-Length: 3831[EOL]"
[DEBUG] wire - << "X-Cache: MISS from web6.bh.sp1.yahoo.net[EOL]"
[DEBUG] wire - << "Connection: close[EOL]"

[DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
[DEBUG] wire - << "<rsp stat="ok"
xmlns:georss="http://www.georss.org/georss">[\n]"
[DEBUG] wire - << "  <user writable="true"
located-at="2008-11-07T14:20:50-08:00" token="gvPAzDEbd2gh"
readable="true">[\n]"
[DEBUG] wire - << "    <location-hierarchy
timezone="America/Los_Angeles">[\n]"
[DEBUG] wire - << "      <location best-guess="true">[\n]"
[DEBUG] wire - << "        <georss:point>45.5334815979
-122.6915664673</georss:point>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>0</level>[\n]"
[DEBUG] wire - << "        <level-name>exact</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>1945 NW Quimby St, Portland,
OR</name>[\n]"
[DEBUG] wire - << "        <normal-name>97209</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="false">JYFOR6.YA5ubOFu48g</place-id>[\n]"
[DEBUG] wire - << "        <woeid
exact-match="false">12798510</woeid>[\n]"
[DEBUG] wire - << "
<query>address=1945%20NW%20Quimby,%20Portland,%20Oregon,%20USA</query>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>45.5228996277 -122.6954574585
45.5440216064 -122.6675415039</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>1</level>[\n]"
[DEBUG] wire - << "        <level-name>postal</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>Portland, OR 97209</name>[\n]"
[DEBUG] wire - << "        <normal-name>97209</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">JYFOR6.YA5ubOFu48g</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">12798510</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>45.520450592 -122.7116317749
45.5499916077 -122.6694488525</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>2</level>[\n]"
[DEBUG] wire - << "        <level-name>neighborhood</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>NW Portland, Portland, OR</name>[\n]"
[DEBUG] wire - << "        <normal-name>NW Portland</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">S5980PybCZ7ZL9WHpA</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">28288854</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>45.4028511047 -122.8665771484
45.6728286743 -122.4571304321</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>3</level>[\n]"
[DEBUG] wire - << "        <level-name>city</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>Portland, OR</name>[\n]"
[DEBUG] wire - << "        <normal-name>Portland</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">RlEYPWubBZtlFXkb</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">2475687</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>45.4323616028 -122.9292602539
45.7285995483 -121.8203964233</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>4</level>[\n]"
[DEBUG] wire - << "        <level-name>region</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>Multnomah County, Oregon</name>[\n]"
[DEBUG] wire - << "        <normal-name>Multnomah</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">AHzl7sWYA5mP8oDGHg</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">12589717</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>41.9917984009 -124.6067733765
46.2910194397 -116.4631271362</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>5</level>[\n]"
[DEBUG] wire - << "        <level-name>state</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>Oregon</name>[\n]"
[DEBUG] wire - << "        <normal-name>Oregon</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">4vvLDQabApjbhCKB</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">2347596</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "      <location best-guess="false">[\n]"
[DEBUG] wire - << "        <georss:box>18.9108390808 -167.2764129639
72.8960571289 -66.6879425049</georss:box>[\n]"
[DEBUG] wire - << "        <label></label>[\n]"
[DEBUG] wire - << "        <level>6</level>[\n]"
[DEBUG] wire - << "        <level-name>country</level-name>[\n]"
[DEBUG] wire - << "
<located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
[DEBUG] wire - << "        <name>United States</name>[\n]"
[DEBUG] wire - << "        <normal-name>United States</normal-name>[\n]"
[DEBUG] wire - << "        <place-id
exact-match="true">4KO02SibApitvSBieQ</place-id>[\n]"
[DEBUG] wire - << "        <woeid exact-match="true">23424977</woeid>[\n]"
[DEBUG] wire - << "      </location>[\n]"
[DEBUG] wire - << "    </location-hierarchy>[\n]"
[DEBUG] wire - << "  </user>[\n]"
[DEBUG] wire - << "</rsp>[\n]"

Hi Dorzey.

It's not documented, but you can use the "w" parameter in the Weather
API to provide a WOEID (that you get from Fire Eagle).  That's what
the Weather Widget does.

seth

On Mon, Nov 3, 2008 at 2:27 AM, paulsdoran <dorzey@...> wrote:
> Sorry, I should have said that I was in need of international weather;
> or at least European.
>
> Thanks.
>
> dorzey
>
> --- In fireeagle@yahoogroups.com, aymanshamma <no_reply@...> wrote:
>>
>> Hi Dorzey,
>>
>> The Y!API for weather allows you to pass a postal code:
>>
>> http://weather.yahooapis.com/forecastrss?p=94089
>>
>> which will work if you only need weather inside the USA.
>>
>> Do you need international weather?
>>
>> -ayman.
>>
>>
>> --- In fireeagle@yahoogroups.com, "paulsdoran" <dorzey@> wrote:
>> >
>> > Hello,
>> >
>> > I've just started to play around with the Fire Eagle API. I wish to
>> > use my current location to get a weather forecast for where I am from
>> > Yahoo! Weather. However, Yahoo! Weather uses 'Location ID' in its
>> > request URL (http://developer.yahoo.com/weather/).
>> >
>> > I can't find any documentation on how to combine Fire Eagle and Yahoo!
>> > Weather. I'm aware that the Mac wdiget
>> > (http://widgets.fireeagle.yahoo.net/) does what I want; I just want to
>> > know how it did it.
>> >
>> > Hope someone can help. Thanks.
>> >
>> > dorzey
>> >
>>
>
>

Your request looks right, so I'm not sure why it's getting a gzipped
response.  It doesn't have all of the headers that Firebug shows me
(in the network tab, open the GET fireeagle.yahoo.net and look at the
request/response headers), but I don't know which would prevent it
from deciding to send you a gzipped response.  Maybe the Accepts
header?

Are you getting correctly gzipped responses when testing it against
other sites that you know gzip their responses?

seth

On Fri, Nov 7, 2008 at 2:43 PM, jfireeagle <sean@...> wrote:
>
>> We already do (YSlow will confirm this for you). However, you
>> may need to send:
>>
>> Accept-Encoding: gzip, deflate
>>
>> seth
>
> I sent a request to Fire Eagle a few moments ago. The request uses
> the "Accept-Encoding: gzip, deflate" header.
>
> Fire Eagle's response did not have a "Content-Encoding: gzip" header.
>
> Can you tell me if there is something wrong with my request?
>
> Request
> =======
>
> [DEBUG] wire - >> "GET
>
/api/0.1/user?oauth_token=gvPAzDEbd2gh&oauth_consumer_key=aCk6Ghm7cUSI&oauth_sig\
nature_method=HMAC-SHA1&oauth_timestamp=1226096451&oauth_nonce=12260964514094510\
00&oauth_version=1.0&oauth_signature=3m0SDzL%2BGaM0TZ8%2BWvqJDqQx5KM%3D
> HTTP/1.1[EOL]"
> [DEBUG] wire - >> "Host: fireeagle.yahooapis.com[EOL]"
> [DEBUG] wire - >> "Connection: Keep-Alive[EOL]"
> [DEBUG] wire - >> "User-Agent: Apache-HttpClient/4.0-beta1 (java
> 1.4)[EOL]"
> [DEBUG] wire - >> "Cookie:
>
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4Cgmy5TIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5d8668423e17a97\
9e865a9641aea93ce63a6f64a[EOL]"
> [DEBUG] wire - >> "Cookie2: $Version=1[EOL]"
> [DEBUG] wire - >> "Accept-Encoding: gzip, deflate[EOL]"
> [DEBUG] wire - >> "[EOL]"
>
> Response
> ========
>
> [DEBUG] wire - << "HTTP/1.1 200 OK[EOL]"
> [DEBUG] wire - << "Date: Fri, 07 Nov 2008 22:20:51 GMT[EOL]"
> [DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
> CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
> DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
> STA POL HEA PRE GOV"[EOL]"
> [DEBUG] wire - << "Content-Type: application/xml; charset=utf-8[EOL]"
> [DEBUG] wire - << "Set-Cookie:
>
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4D0mTpTIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--858ca7c87d1eec8\
20b4a39e8eacd6cdeabd3279b;
> path=/[EOL]"
> [DEBUG] wire - << "Status: 200 OK[EOL]"
> [DEBUG] wire - << "X-Runtime: 0.12992[EOL]"
> [DEBUG] wire - << "ETag: "7537e3e2654bf4c8ede462c2e6e7160e"[EOL]"
> [DEBUG] wire - << "X-XRDS-Location:
> http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
> [DEBUG] wire - << "Cache-Control: private, max-age=0,
> must-revalidate[EOL]"
> [DEBUG] wire - << "Content-Length: 3831[EOL]"
> [DEBUG] wire - << "X-Cache: MISS from web6.bh.sp1.yahoo.net[EOL]"
> [DEBUG] wire - << "Connection: close[EOL]"
>
> [DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
> [DEBUG] wire - << "<rsp stat="ok"
> xmlns:georss="http://www.georss.org/georss">[\n]"
> [DEBUG] wire - << " <user writable="true"
> located-at="2008-11-07T14:20:50-08:00" token="gvPAzDEbd2gh"
> readable="true">[\n]"
> [DEBUG] wire - << " <location-hierarchy
> timezone="America/Los_Angeles">[\n]"
> [DEBUG] wire - << " <location best-guess="true">[\n]"
> [DEBUG] wire - << " <georss:point>45.5334815979
> -122.6915664673</georss:point>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>0</level>[\n]"
> [DEBUG] wire - << " <level-name>exact</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>1945 NW Quimby St, Portland,
> OR</name>[\n]"
> [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="false">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> [DEBUG] wire - << " <woeid
> exact-match="false">12798510</woeid>[\n]"
> [DEBUG] wire - << "
> <query>address=1945%20NW%20Quimby,%20Portland,%20Oregon,%20USA</query>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>45.5228996277 -122.6954574585
> 45.5440216064 -122.6675415039</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>1</level>[\n]"
> [DEBUG] wire - << " <level-name>postal</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>Portland, OR 97209</name>[\n]"
> [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">12798510</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>45.520450592 -122.7116317749
> 45.5499916077 -122.6694488525</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>2</level>[\n]"
> [DEBUG] wire - << " <level-name>neighborhood</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>NW Portland, Portland, OR</name>[\n]"
> [DEBUG] wire - << " <normal-name>NW Portland</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">S5980PybCZ7ZL9WHpA</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">28288854</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>45.4028511047 -122.8665771484
> 45.6728286743 -122.4571304321</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>3</level>[\n]"
> [DEBUG] wire - << " <level-name>city</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>Portland, OR</name>[\n]"
> [DEBUG] wire - << " <normal-name>Portland</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">RlEYPWubBZtlFXkb</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">2475687</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>45.4323616028 -122.9292602539
> 45.7285995483 -121.8203964233</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>4</level>[\n]"
> [DEBUG] wire - << " <level-name>region</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>Multnomah County, Oregon</name>[\n]"
> [DEBUG] wire - << " <normal-name>Multnomah</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">AHzl7sWYA5mP8oDGHg</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">12589717</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>41.9917984009 -124.6067733765
> 46.2910194397 -116.4631271362</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>5</level>[\n]"
> [DEBUG] wire - << " <level-name>state</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>Oregon</name>[\n]"
> [DEBUG] wire - << " <normal-name>Oregon</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">4vvLDQabApjbhCKB</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">2347596</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " <location best-guess="false">[\n]"
> [DEBUG] wire - << " <georss:box>18.9108390808 -167.2764129639
> 72.8960571289 -66.6879425049</georss:box>[\n]"
> [DEBUG] wire - << " <label></label>[\n]"
> [DEBUG] wire - << " <level>6</level>[\n]"
> [DEBUG] wire - << " <level-name>country</level-name>[\n]"
> [DEBUG] wire - << "
> <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> [DEBUG] wire - << " <name>United States</name>[\n]"
> [DEBUG] wire - << " <normal-name>United States</normal-name>[\n]"
> [DEBUG] wire - << " <place-id
> exact-match="true">4KO02SibApitvSBieQ</place-id>[\n]"
> [DEBUG] wire - << " <woeid exact-match="true">23424977</woeid>[\n]"
> [DEBUG] wire - << " </location>[\n]"
> [DEBUG] wire - << " </location-hierarchy>[\n]"
> [DEBUG] wire - << " </user>[\n]"
> [DEBUG] wire - << "</rsp>[\n]"
>
>

I have tested Apache HttpClient against another public
REST web service. The other REST web service sends
a gzip compressed response and the 'Content-Encoding: gzip'
header.

Sean

--- In fireeagle@yahoogroups.com, "Seth Fitzsimmons" <seth@...> wrote:
>
> Your request looks right, so I'm not sure why it's getting a gzipped
> response.  It doesn't have all of the headers that Firebug shows me
> (in the network tab, open the GET fireeagle.yahoo.net and look at the
> request/response headers), but I don't know which would prevent it
> from deciding to send you a gzipped response.  Maybe the Accepts
> header?
>
> Are you getting correctly gzipped responses when testing it against
> other sites that you know gzip their responses?
>
> seth
>
> On Fri, Nov 7, 2008 at 2:43 PM, jfireeagle <sean@...> wrote:
> >
> >> We already do (YSlow will confirm this for you). However, you
> >> may need to send:
> >>
> >> Accept-Encoding: gzip, deflate
> >>
> >> seth
> >
> > I sent a request to Fire Eagle a few moments ago. The request uses
> > the "Accept-Encoding: gzip, deflate" header.
> >
> > Fire Eagle's response did not have a "Content-Encoding: gzip" header.
> >
> > Can you tell me if there is something wrong with my request?
> >
> > Request
> > =======
> >
> > [DEBUG] wire - >> "GET
> >
/api/0.1/user?oauth_token=gvPAzDEbd2gh&oauth_consumer_key=aCk6Ghm7cUSI&oauth_sig\
nature_method=HMAC-SHA1&oauth_timestamp=1226096451&oauth_nonce=12260964514094510\
00&oauth_version=1.0&oauth_signature=3m0SDzL%2BGaM0TZ8%2BWvqJDqQx5KM%3D
> > HTTP/1.1[EOL]"
> > [DEBUG] wire - >> "Host: fireeagle.yahooapis.com[EOL]"
> > [DEBUG] wire - >> "Connection: Keep-Alive[EOL]"
> > [DEBUG] wire - >> "User-Agent: Apache-HttpClient/4.0-beta1 (java
> > 1.4)[EOL]"
> > [DEBUG] wire - >> "Cookie:
> >
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4Cgmy5TIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5d8668423e17a97\
9e865a9641aea93ce63a6f64a[EOL]"
> > [DEBUG] wire - >> "Cookie2: $Version=1[EOL]"
> > [DEBUG] wire - >> "Accept-Encoding: gzip, deflate[EOL]"
> > [DEBUG] wire - >> "[EOL]"
> >
> > Response
> > ========
> >
> > [DEBUG] wire - << "HTTP/1.1 200 OK[EOL]"
> > [DEBUG] wire - << "Date: Fri, 07 Nov 2008 22:20:51 GMT[EOL]"
> > [DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
> > CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
> > DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
> > STA POL HEA PRE GOV"[EOL]"
> > [DEBUG] wire - << "Content-Type: application/xml; charset=utf-8[EOL]"
> > [DEBUG] wire - << "Set-Cookie:
> >
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4D0mTpTIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--858ca7c87d1eec8\
20b4a39e8eacd6cdeabd3279b;
> > path=/[EOL]"
> > [DEBUG] wire - << "Status: 200 OK[EOL]"
> > [DEBUG] wire - << "X-Runtime: 0.12992[EOL]"
> > [DEBUG] wire - << "ETag: "7537e3e2654bf4c8ede462c2e6e7160e"[EOL]"
> > [DEBUG] wire - << "X-XRDS-Location:
> > http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
> > [DEBUG] wire - << "Cache-Control: private, max-age=0,
> > must-revalidate[EOL]"
> > [DEBUG] wire - << "Content-Length: 3831[EOL]"
> > [DEBUG] wire - << "X-Cache: MISS from web6.bh.sp1.yahoo.net[EOL]"
> > [DEBUG] wire - << "Connection: close[EOL]"
> >
> > [DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
> > [DEBUG] wire - << "<rsp stat="ok"
> > xmlns:georss="http://www.georss.org/georss">[\n]"
> > [DEBUG] wire - << " <user writable="true"
> > located-at="2008-11-07T14:20:50-08:00" token="gvPAzDEbd2gh"
> > readable="true">[\n]"
> > [DEBUG] wire - << " <location-hierarchy
> > timezone="America/Los_Angeles">[\n]"
> > [DEBUG] wire - << " <location best-guess="true">[\n]"
> > [DEBUG] wire - << " <georss:point>45.5334815979
> > -122.6915664673</georss:point>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>0</level>[\n]"
> > [DEBUG] wire - << " <level-name>exact</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>1945 NW Quimby St, Portland,
> > OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="false">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> > [DEBUG] wire - << " <woeid
> > exact-match="false">12798510</woeid>[\n]"
> > [DEBUG] wire - << "
> >
<query>address=1945%20NW%20Quimby,%20Portland,%20Oregon,%20USA</query>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.5228996277 -122.6954574585
> > 45.5440216064 -122.6675415039</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>1</level>[\n]"
> > [DEBUG] wire - << " <level-name>postal</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Portland, OR 97209</name>[\n]"
> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">12798510</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.520450592 -122.7116317749
> > 45.5499916077 -122.6694488525</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>2</level>[\n]"
> > [DEBUG] wire - << " <level-name>neighborhood</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>NW Portland, Portland, OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>NW Portland</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">S5980PybCZ7ZL9WHpA</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">28288854</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.4028511047 -122.8665771484
> > 45.6728286743 -122.4571304321</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>3</level>[\n]"
> > [DEBUG] wire - << " <level-name>city</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Portland, OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Portland</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">RlEYPWubBZtlFXkb</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">2475687</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.4323616028 -122.9292602539
> > 45.7285995483 -121.8203964233</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>4</level>[\n]"
> > [DEBUG] wire - << " <level-name>region</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Multnomah County, Oregon</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Multnomah</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">AHzl7sWYA5mP8oDGHg</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">12589717</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>41.9917984009 -124.6067733765
> > 46.2910194397 -116.4631271362</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>5</level>[\n]"
> > [DEBUG] wire - << " <level-name>state</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Oregon</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Oregon</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">4vvLDQabApjbhCKB</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">2347596</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>18.9108390808 -167.2764129639
> > 72.8960571289 -66.6879425049</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>6</level>[\n]"
> > [DEBUG] wire - << " <level-name>country</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>United States</name>[\n]"
> > [DEBUG] wire - << " <normal-name>United States</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">4KO02SibApitvSBieQ</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">23424977</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " </location-hierarchy>[\n]"
> > [DEBUG] wire - << " </user>[\n]"
> > [DEBUG] wire - << "</rsp>[\n]"
> >
> >
>

Regarding Firebug:    are you sending the GET request to
fireeagle.yahoo.net or to fireeagle.yahooapis.com ?

I can see a gzip compressed response from fireeagle.yahoo.net

I do not see a gzip compressed response from fireeagle.yahooapis.com

Sean


--- In fireeagle@yahoogroups.com, "Seth Fitzsimmons" <seth@...> wrote:
>
> Your request looks right, so I'm not sure why it's getting a gzipped
> response.  It doesn't have all of the headers that Firebug shows me
> (in the network tab, open the GET fireeagle.yahoo.net and look at the
> request/response headers), but I don't know which would prevent it
> from deciding to send you a gzipped response.  Maybe the Accepts
> header?
>
> Are you getting correctly gzipped responses when testing it against
> other sites that you know gzip their responses?
>
> seth
>
> On Fri, Nov 7, 2008 at 2:43 PM, jfireeagle <sean@...> wrote:
> >
> >> We already do (YSlow will confirm this for you). However, you
> >> may need to send:
> >>
> >> Accept-Encoding: gzip, deflate
> >>
> >> seth
> >
> > I sent a request to Fire Eagle a few moments ago. The request uses
> > the "Accept-Encoding: gzip, deflate" header.
> >
> > Fire Eagle's response did not have a "Content-Encoding: gzip" header.
> >
> > Can you tell me if there is something wrong with my request?
> >
> > Request
> > =======
> >
> > [DEBUG] wire - >> "GET
> >
/api/0.1/user?oauth_token=gvPAzDEbd2gh&oauth_consumer_key=aCk6Ghm7cUSI&oauth_sig\
nature_method=HMAC-SHA1&oauth_timestamp=1226096451&oauth_nonce=12260964514094510\
00&oauth_version=1.0&oauth_signature=3m0SDzL%2BGaM0TZ8%2BWvqJDqQx5KM%3D
> > HTTP/1.1[EOL]"
> > [DEBUG] wire - >> "Host: fireeagle.yahooapis.com[EOL]"
> > [DEBUG] wire - >> "Connection: Keep-Alive[EOL]"
> > [DEBUG] wire - >> "User-Agent: Apache-HttpClient/4.0-beta1 (java
> > 1.4)[EOL]"
> > [DEBUG] wire - >> "Cookie:
> >
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4Cgmy5TIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5d8668423e17a97\
9e865a9641aea93ce63a6f64a[EOL]"
> > [DEBUG] wire - >> "Cookie2: $Version=1[EOL]"
> > [DEBUG] wire - >> "Accept-Encoding: gzip, deflate[EOL]"
> > [DEBUG] wire - >> "[EOL]"
> >
> > Response
> > ========
> >
> > [DEBUG] wire - << "HTTP/1.1 200 OK[EOL]"
> > [DEBUG] wire - << "Date: Fri, 07 Nov 2008 22:20:51 GMT[EOL]"
> > [DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
> > CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
> > DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
> > STA POL HEA PRE GOV"[EOL]"
> > [DEBUG] wire - << "Content-Type: application/xml; charset=utf-8[EOL]"
> > [DEBUG] wire - << "Set-Cookie:
> >
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4D0mTpTIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--858ca7c87d1eec8\
20b4a39e8eacd6cdeabd3279b;
> > path=/[EOL]"
> > [DEBUG] wire - << "Status: 200 OK[EOL]"
> > [DEBUG] wire - << "X-Runtime: 0.12992[EOL]"
> > [DEBUG] wire - << "ETag: "7537e3e2654bf4c8ede462c2e6e7160e"[EOL]"
> > [DEBUG] wire - << "X-XRDS-Location:
> > http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
> > [DEBUG] wire - << "Cache-Control: private, max-age=0,
> > must-revalidate[EOL]"
> > [DEBUG] wire - << "Content-Length: 3831[EOL]"
> > [DEBUG] wire - << "X-Cache: MISS from web6.bh.sp1.yahoo.net[EOL]"
> > [DEBUG] wire - << "Connection: close[EOL]"
> >
> > [DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
> > [DEBUG] wire - << "<rsp stat="ok"
> > xmlns:georss="http://www.georss.org/georss">[\n]"
> > [DEBUG] wire - << " <user writable="true"
> > located-at="2008-11-07T14:20:50-08:00" token="gvPAzDEbd2gh"
> > readable="true">[\n]"
> > [DEBUG] wire - << " <location-hierarchy
> > timezone="America/Los_Angeles">[\n]"
> > [DEBUG] wire - << " <location best-guess="true">[\n]"
> > [DEBUG] wire - << " <georss:point>45.5334815979
> > -122.6915664673</georss:point>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>0</level>[\n]"
> > [DEBUG] wire - << " <level-name>exact</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>1945 NW Quimby St, Portland,
> > OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="false">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> > [DEBUG] wire - << " <woeid
> > exact-match="false">12798510</woeid>[\n]"
> > [DEBUG] wire - << "
> >
<query>address=1945%20NW%20Quimby,%20Portland,%20Oregon,%20USA</query>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.5228996277 -122.6954574585
> > 45.5440216064 -122.6675415039</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>1</level>[\n]"
> > [DEBUG] wire - << " <level-name>postal</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Portland, OR 97209</name>[\n]"
> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">JYFOR6.YA5ubOFu48g</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">12798510</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.520450592 -122.7116317749
> > 45.5499916077 -122.6694488525</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>2</level>[\n]"
> > [DEBUG] wire - << " <level-name>neighborhood</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>NW Portland, Portland, OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>NW Portland</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">S5980PybCZ7ZL9WHpA</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">28288854</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.4028511047 -122.8665771484
> > 45.6728286743 -122.4571304321</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>3</level>[\n]"
> > [DEBUG] wire - << " <level-name>city</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Portland, OR</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Portland</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">RlEYPWubBZtlFXkb</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">2475687</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>45.4323616028 -122.9292602539
> > 45.7285995483 -121.8203964233</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>4</level>[\n]"
> > [DEBUG] wire - << " <level-name>region</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Multnomah County, Oregon</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Multnomah</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">AHzl7sWYA5mP8oDGHg</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">12589717</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>41.9917984009 -124.6067733765
> > 46.2910194397 -116.4631271362</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>5</level>[\n]"
> > [DEBUG] wire - << " <level-name>state</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>Oregon</name>[\n]"
> > [DEBUG] wire - << " <normal-name>Oregon</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">4vvLDQabApjbhCKB</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">2347596</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " <location best-guess="false">[\n]"
> > [DEBUG] wire - << " <georss:box>18.9108390808 -167.2764129639
> > 72.8960571289 -66.6879425049</georss:box>[\n]"
> > [DEBUG] wire - << " <label></label>[\n]"
> > [DEBUG] wire - << " <level>6</level>[\n]"
> > [DEBUG] wire - << " <level-name>country</level-name>[\n]"
> > [DEBUG] wire - << "
> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
> > [DEBUG] wire - << " <name>United States</name>[\n]"
> > [DEBUG] wire - << " <normal-name>United States</normal-name>[\n]"
> > [DEBUG] wire - << " <place-id
> > exact-match="true">4KO02SibApitvSBieQ</place-id>[\n]"
> > [DEBUG] wire - << " <woeid exact-match="true">23424977</woeid>[\n]"
> > [DEBUG] wire - << " </location>[\n]"
> > [DEBUG] wire - << " </location-hierarchy>[\n]"
> > [DEBUG] wire - << " </user>[\n]"
> > [DEBUG] wire - << "</rsp>[\n]"
> >
> >
>

Good find.  I'll see if I can figure out why that's the case.

seth

On Fri, Nov 7, 2008 at 3:57 PM, jfireeagle <sean@...> wrote:
>
>
> Regarding Firebug: are you sending the GET request to
> fireeagle.yahoo.net or to fireeagle.yahooapis.com ?
>
> I can see a gzip compressed response from fireeagle.yahoo.net
>
> I do not see a gzip compressed response from fireeagle.yahooapis.com
>
> Sean
>
> --- In fireeagle@yahoogroups.com, "Seth Fitzsimmons" <seth@...> wrote:
>>
>> Your request looks right, so I'm not sure why it's getting a gzipped
>> response. It doesn't have all of the headers that Firebug shows me
>> (in the network tab, open the GET fireeagle.yahoo.net and look at the
>> request/response headers), but I don't know which would prevent it
>> from deciding to send you a gzipped response. Maybe the Accepts
>> header?
>>
>> Are you getting correctly gzipped responses when testing it against
>> other sites that you know gzip their responses?
>>
>> seth
>>
>> On Fri, Nov 7, 2008 at 2:43 PM, jfireeagle <sean@...> wrote:
>> >
>> >> We already do (YSlow will confirm this for you). However, you
>> >> may need to send:
>> >>
>> >> Accept-Encoding: gzip, deflate
>> >>
>> >> seth
>> >
>> > I sent a request to Fire Eagle a few moments ago. The request uses
>> > the "Accept-Encoding: gzip, deflate" header.
>> >
>> > Fire Eagle's response did not have a "Content-Encoding: gzip" header.
>> >
>> > Can you tell me if there is something wrong with my request?
>> >
>> > Request
>> > =======
>> >
>> > [DEBUG] wire - >> "GET
>> >
>
/api/0.1/user?oauth_token=gvPAzDEbd2gh&oauth_consumer_key=aCk6Ghm7cUSI&oauth_sig\
nature_method=HMAC-SHA1&oauth_timestamp=1226096451&oauth_nonce=12260964514094510\
00&oauth_version=1.0&oauth_signature=3m0SDzL%2BGaM0TZ8%2BWvqJDqQx5KM%3D
>> > HTTP/1.1[EOL]"
>> > [DEBUG] wire - >> "Host: fireeagle.yahooapis.com[EOL]"
>> > [DEBUG] wire - >> "Connection: Keep-Alive[EOL]"
>> > [DEBUG] wire - >> "User-Agent: Apache-HttpClient/4.0-beta1 (java
>> > 1.4)[EOL]"
>> > [DEBUG] wire - >> "Cookie:
>> >
>
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4Cgmy5TIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--5d8668423e17a97\
9e865a9641aea93ce63a6f64a[EOL]"
>> > [DEBUG] wire - >> "Cookie2: $Version=1[EOL]"
>> > [DEBUG] wire - >> "Accept-Encoding: gzip, deflate[EOL]"
>> > [DEBUG] wire - >> "[EOL]"
>> >
>> > Response
>> > ========
>> >
>> > [DEBUG] wire - << "HTTP/1.1 200 OK[EOL]"
>> > [DEBUG] wire - << "Date: Fri, 07 Nov 2008 22:20:51 GMT[EOL]"
>> > [DEBUG] wire - << "P3P: policyref="http://p3p.yahoo.com/w3c/p3p.xml",
>> > CP="CAO DSP COR CUR ADM DEV TAI PSA PSD IVAi IVDi CONi TELo OTPi OUR
>> > DELi SAMi OTRi UNRi PUBi IND PHY ONL UNI PUR FIN COM NAV INT DEM CNT
>> > STA POL HEA PRE GOV"[EOL]"
>> > [DEBUG] wire - << "Content-Type: application/xml; charset=utf-8[EOL]"
>> > [DEBUG] wire - << "Set-Cookie:
>> >
>
_pinpoint_session=BAh7BzoQZXhwaXJ5X3RpbWV1OglUaW1lDfcoG4D0mTpTIgpmbGFzaElDOidB%2\
50AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--858ca7c87d1eec8\
20b4a39e8eacd6cdeabd3279b;
>> > path=/[EOL]"
>> > [DEBUG] wire - << "Status: 200 OK[EOL]"
>> > [DEBUG] wire - << "X-Runtime: 0.12992[EOL]"
>> > [DEBUG] wire - << "ETag: "7537e3e2654bf4c8ede462c2e6e7160e"[EOL]"
>> > [DEBUG] wire - << "X-XRDS-Location:
>> > http://fireeagle.yahoo.net/fireeagle.xrds[EOL]"
>> > [DEBUG] wire - << "Cache-Control: private, max-age=0,
>> > must-revalidate[EOL]"
>> > [DEBUG] wire - << "Content-Length: 3831[EOL]"
>> > [DEBUG] wire - << "X-Cache: MISS from web6.bh.sp1.yahoo.net[EOL]"
>> > [DEBUG] wire - << "Connection: close[EOL]"
>> >
>> > [DEBUG] wire - << "<?xml version="1.0" encoding="UTF-8"?>[\n]"
>> > [DEBUG] wire - << "<rsp stat="ok"
>> > xmlns:georss="http://www.georss.org/georss">[\n]"
>> > [DEBUG] wire - << " <user writable="true"
>> > located-at="2008-11-07T14:20:50-08:00" token="gvPAzDEbd2gh"
>> > readable="true">[\n]"
>> > [DEBUG] wire - << " <location-hierarchy
>> > timezone="America/Los_Angeles">[\n]"
>> > [DEBUG] wire - << " <location best-guess="true">[\n]"
>> > [DEBUG] wire - << " <georss:point>45.5334815979
>> > -122.6915664673</georss:point>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>0</level>[\n]"
>> > [DEBUG] wire - << " <level-name>exact</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>1945 NW Quimby St, Portland,
>> > OR</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="false">JYFOR6.YA5ubOFu48g</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid
>> > exact-match="false">12798510</woeid>[\n]"
>> > [DEBUG] wire - << "
>> >
> <query>address=1945%20NW%20Quimby,%20Portland,%20Oregon,%20USA</query>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>45.5228996277 -122.6954574585
>> > 45.5440216064 -122.6675415039</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>1</level>[\n]"
>> > [DEBUG] wire - << " <level-name>postal</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>Portland, OR 97209</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>97209</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">JYFOR6.YA5ubOFu48g</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">12798510</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>45.520450592 -122.7116317749
>> > 45.5499916077 -122.6694488525</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>2</level>[\n]"
>> > [DEBUG] wire - << " <level-name>neighborhood</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>NW Portland, Portland, OR</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>NW Portland</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">S5980PybCZ7ZL9WHpA</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">28288854</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>45.4028511047 -122.8665771484
>> > 45.6728286743 -122.4571304321</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>3</level>[\n]"
>> > [DEBUG] wire - << " <level-name>city</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>Portland, OR</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>Portland</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">RlEYPWubBZtlFXkb</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">2475687</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>45.4323616028 -122.9292602539
>> > 45.7285995483 -121.8203964233</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>4</level>[\n]"
>> > [DEBUG] wire - << " <level-name>region</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>Multnomah County, Oregon</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>Multnomah</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">AHzl7sWYA5mP8oDGHg</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">12589717</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>41.9917984009 -124.6067733765
>> > 46.2910194397 -116.4631271362</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>5</level>[\n]"
>> > [DEBUG] wire - << " <level-name>state</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>Oregon</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>Oregon</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">4vvLDQabApjbhCKB</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">2347596</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " <location best-guess="false">[\n]"
>> > [DEBUG] wire - << " <georss:box>18.9108390808 -167.2764129639
>> > 72.8960571289 -66.6879425049</georss:box>[\n]"
>> > [DEBUG] wire - << " <label></label>[\n]"
>> > [DEBUG] wire - << " <level>6</level>[\n]"
>> > [DEBUG] wire - << " <level-name>country</level-name>[\n]"
>> > [DEBUG] wire - << "
>> > <located-at>2008-11-07T14:20:50-08:00</located-at>[\n]"
>> > [DEBUG] wire - << " <name>United States</name>[\n]"
>> > [DEBUG] wire - << " <normal-name>United States</normal-name>[\n]"
>> > [DEBUG] wire - << " <place-id
>> > exact-match="true">4KO02SibApitvSBieQ</place-id>[\n]"
>> > [DEBUG] wire - << " <woeid exact-match="true">23424977</woeid>[\n]"
>> > [DEBUG] wire - << " </location>[\n]"
>> > [DEBUG] wire - << " </location-hierarchy>[\n]"
>> > [DEBUG] wire - << " </user>[\n]"
>> > [DEBUG] wire - << "</rsp>[\n]"
>> >
>> >
>>
>
>

my team and I are working on a location aware project for law enforcement, and
would like to
find a developer or developer team to assist.

Specific tasks include video on the handset as displayed content using fireeagle
as a trigger.

Interested parties can respond to this post, and I'll answer back direct.

Dan

I'm looking for a simple app that will constantly broadcast my
location from my blackberry and nokia.

I'm not entirely satisfied with the accuracy and battery drain of the
Navizon client.

Are there alternatives I can look at?

Antony

Hi Armand.

The correct link for downloading is:
http://j2me.fireeagle.yahoo.net/j2me/FireEagleUpdater.jar

seth

On Wed, Nov 12, 2008 at 12:03 AM, Armand du Plessis
<armanddp@...> wrote:
> Hi Chris,
>
> The download link also seems to be unavailable at the moment.
> - Armand
>
> On Wed, Nov 12, 2008 at 1:06 AM, Chris Martin <cjmartin@...>
> wrote:
>>
>> I would recommend looking into the J2ME updater
>> - http://j2me.fireeagle.yahoo.net/j2me/ it's not currently listed in our
>> gallery... we're working on that.
>>
>> -Chris
>> On Nov 11, 2008, at 1:38 PM, abrydon wrote:
>>
>> I'm looking for a simple app that will constantly broadcast my
>> location from my blackberry and nokia.
>>
>> I'm not entirely satisfied with the accuracy and battery drain of the
>> Navizon client.
>>
>> Are there alternatives I can look at?
>>
>> Antony
>>
>>
>
>

Hello,


could someone please point me toward an easy solution on how to
calculate local time from timezone and timestamp?

A couple of EagleFeed users requested that.

I guess, I will need a database with timezone -> zone-offset mapping
and DST parameters. Do you know where I could get these information as
a table or database?


Thanks a lot,

Richie

--- In fireeagle@yahoogroups.com, "tones_space" <mctones@...> wrote:
>
> > > Perhaps you could return a GMT offset as well?
> > >
> > > E.g.:
> > >> { "user": { ..., "token": "blah", "timezone":
"America/Los_Angeles",
> > > "tzoffset": "-8" } }
> >
> > Unfortunately, it's not that easy, as GMT offsets vary by season; we
> > could return the offset at update-time, but it seems easier to just
> > support names and leave that to client implementations.
>
> I quite like the approach of the earthtools web service for handling
> this, as an example take a look at the results for LA:
>
> http://www.earthtools.org/timezone/34.052187/-118.243425
>
> (more info http://www.earthtools.org/webservices.htm#timezone)
>
> I appreciate that a similar approach is quite complicated/resource
> intensive, but one of the things that struck me about Fire Eagle as my
> location broker is you chuck it anything and it does all the hard work
> for you and your devices/services. Can we rely on third party apps to
> apply (complicated)  DST rules consistently; I would feel more
> confident in Fire Eagle doing that.
>
> Anyways, I digress; something is better than nothing :-)
>

Hi Richie.

The simplest way is to lean on your OS's TZ implementation:
$ TZ=America/New_York date -r 1226531571

tz is the database that most systems seem to use; if you set the TZ
environment, time conversions should be handled for you.  MySQL will
also do timezone conversions for you, if you're using that:
http://dev.mysql.com/doc/refman/5.0/en/time-zone-support.html

seth

On Wed, Nov 12, 2008 at 2:36 PM, richard_metzler
<richard@...> wrote:
> Hello,
>
> could someone please point me toward an easy solution on how to
> calculate local time from timezone and timestamp?
>
> A couple of EagleFeed users requested that.
>
> I guess, I will need a database with timezone -> zone-offset mapping
> and DST parameters. Do you know where I could get these information as
> a table or database?
>
> Thanks a lot,
>
> Richie
>
> --- In fireeagle@yahoogroups.com, "tones_space" <mctones@...> wrote:
>>
>> > > Perhaps you could return a GMT offset as well?
>> > >
>> > > E.g.:
>> > >> { "user": { ..., "token": "blah", "timezone":
> "America/Los_Angeles",
>> > > "tzoffset": "-8" } }
>> >
>> > Unfortunately, it's not that easy, as GMT offsets vary by season; we
>> > could return the offset at update-time, but it seems easier to just
>> > support names and leave that to client implementations.
>>
>> I quite like the approach of the earthtools web service for handling
>> this, as an example take a look at the results for LA:
>>
>> http://www.earthtools.org/timezone/34.052187/-118.243425
>>
>> (more info http://www.earthtools.org/webservices.htm#timezone)
>>
>> I appreciate that a similar approach is quite complicated/resource
>> intensive, but one of the things that struck me about Fire Eagle as my
>> location broker is you chuck it anything and it does all the hard work
>> for you and your devices/services. Can we rely on third party apps to
>> apply (complicated) DST rules consistently; I would feel more
>> confident in Fire Eagle doing that.
>>
>> Anyways, I digress; something is better than nothing :-)
>>
>
>

EagleFeed is running on Google AppEngine / Python, that's why your
approach won't work.

But I found http://pytz.sourceforge.net/ which seems to do what I want.


Richie

--- In fireeagle@yahoogroups.com, "Seth Fitzsimmons" <seth@...> wrote:
>
> Hi Richie.
>
> The simplest way is to lean on your OS's TZ implementation:
> $ TZ=America/New_York date -r 1226531571
>
> tz is the database that most systems seem to use; if you set the TZ
> environment, time conversions should be handled for you.  MySQL will
> also do timezone conversions for you, if you're using that:
> http://dev.mysql.com/doc/refman/5.0/en/time-zone-support.html
>
> seth
>
> On Wed, Nov 12, 2008 at 2:36 PM, richard_metzler
> <richard@...> wrote:
> > Hello,
> >
> > could someone please point me toward an easy solution on how to
> > calculate local time from timezone and timestamp?
> >
> > A couple of EagleFeed users requested that.
> >
> > I guess, I will need a database with timezone -> zone-offset mapping
> > and DST parameters. Do you know where I could get these information as
> > a table or database?
> >
> > Thanks a lot,
> >
> > Richie
> >

Hey guys,

We just got our Twitter stream of updates up and running. Hopefully
this will get updated a little more often than the blog does. We'll be
sticking up links for developers and stuff up there along with the
general updates, so I hope to see some of you following...

http://twitter.com/fireeagle

Tom

I've got two questions today, due to my obviously muddled understanding of OAuth
:-)

I'm trying to build a new FE app that, roughly, tracks a bunch of users and
occasionally sends them alerts based on location.

I'm comfortable with getting users to authorize my app to see their location.

My idea is that there will be a server process that uses /recent to watch
changes in the location of users. It's not clear to me how that server process
needs to authenticate to FE - the /recent documentation indicates that it should
use the General Purpose token and secret ... is it that simple? Just pass in the
token with the call, or does there need to be an exchange at startup? That's
question 1.

The other question regards user authentication. I'd like to piggyback on the
existing FE authentication/authorization mechanism to avoid building my own
user/password system - I have some RESTful APIs that allow users to set up the
notification actions they're interested, and I'd be happy to have them (somehow)
authenticate via FE/Yahoo and then come back to my APIs. I know that I'm waving
my hands furiously here, because I don't quite understand what's going on under
the covers when someone authenticates to FE ... but perhaps someone will clear
it up a bit for me?

Thanks.

Let me ask question 1 a different way:

I have a bare bones python app that looks like

--

from fireeagle_api import FireEagle
import httplib
import oauth

# file to store access tokens
TOKEN_FILE = './notifier.pkl'

SERVER = 'fireeagle.yahooapis.com'

REQUEST_TOKEN_URL = 'https://'+SERVER+'/oauth/request_token'
ACCESS_TOKEN_URL = 'https://'+SERVER+'/oauth/access_token'
AUTHORIZATION_URL = 'http://fireeagle.yahoo.net/oauth/authorize'
QUERY_API_URL = 'https://'+SERVER+'/api/0.1/user'
UPDATE_API_URL = 'https://'+SERVER+'/api/0.1/update'

# key and secret you got from Fire Eagle when registering an application
CONSUMER_KEY = 'x'
CONSUMER_SECRET = 'y'
GENERAL_TOKEN = 'z'
GENERAL_SECRET = 'w'

# main routine
def test_fireeagle():
     fe = FireEagle(CONSUMER_KEY, GENERAL_SECRET)
     #appToken = fe.request_token()
     appToken = GENERAL_TOKEN
     print fe.recent(appToken)

--

So far, I haven't found the right combination of arguments and calls to get
myself a response from fe.recent() - all I can do is generate various errors
like

fireeagle_api.py", line 312, in fetch_response
     raise FireEagleException, msg
fireeagle_api.FireEagleException: Invalid OAuth signature. (Code 23)

and

oauth.py", line 222, in from_consumer_and_token
     parameters['oauth_token'] = token.key
AttributeError: 'str' object has no attribute 'key'

What's the right way to use the GENERAL_TOKEN?

Thanks,
chris

OK, I'm figuring this out....

--

from fireeagle_api import FireEagle
import httplib
import oauth

SERVER = 'fireeagle.yahooapis.com'

REQUEST_TOKEN_URL = 'https://'+SERVER+'/oauth/request_token'
ACCESS_TOKEN_URL = 'https://'+SERVER+'/oauth/access_token'
AUTHORIZATION_URL = 'http://fireeagle.yahoo.net/oauth/authorize'
QUERY_API_URL = 'https://'+SERVER+'/api/0.1/user'
UPDATE_API_URL = 'https://'+SERVER+'/api/0.1/update'

# key and secret you got from Fire Eagle when registering an application
CONSUMER_KEY = 'x'
CONSUMER_SECRET = 'y'
GENERAL_TOKEN = 'z'
GENERAL_SECRET = 'w'

# main routine
def test_fireeagle():
     fe = FireEagle(CONSUMER_KEY, CONSUMER_SECRET)
     appToken = oauth.OAuthToken(GENERAL_TOKEN, GENERAL_SECRET)

     print fe.recent(appToken)

--

That gets me a response of

[{'token': 'aEACzBbMx0KO', 'location': []}]

Which doesn't look exactly like what the API explorer would lead me to believe,
but it's progress...

/recent gives me a response of

[{'token': 'aEACzBbMx0KO', 'location': []}]

I'm suspicious that the location is empty. I'd like to grab the location
associated with the token (that is, the user).

But that's not a "real" token - it's just a key. What's the associated
key/secret to turn it into a token using oauth.OAuthToken? I've tried both
CONSUMER_SECRET and GENERAL_SECRET and always get

fireeagle_api.py", line 312, in fetch_response
     raise FireEagleException, msg
fireeagle_api.FireEagleException: Invalid OAuth signature. (Code 23)

The API explorer leads me to believe that no secret is passed, but the
terminology is really quite confused - OAuth calls it a key, but FE calls it a
secret, usually, but even FE can't keep it straight when discussing CONSUMER vs
GENERAL ...

Hey Chris.

I'm glad to see that you've been making progress.  If you'd like to
receive updates in real-time, you can try out our XMPP pubsub node
(which hasn't been documented yet).  There are Ruby-focused docs and
libs here:
http://github.com/mojodna/fire-hydrant/tree/master

(You can set up the subscription w/ those tools and switch over to
sleekxmpp, xmpp.py, or twisted words to consume the pubsub feed.)

On Thu, Nov 13, 2008 at 3:14 PM, Chris Kantarjiev <ckantarj@...> wrote:
> /recent gives me a response of
>
> [{'token': 'aEACzBbMx0KO', 'location': []}]
>
> I'm suspicious that the location is empty. I'd like to grab the location
> associated with the token (that is, the user).

You'll have to make a second request back to /user w/ the access token
and secret that correspond to the token you want the location for.
(This is all about limiting exposure should certain keys/secrets leak
out.)

> But that's not a "real" token - it's just a key. What's the associated
> key/secret to turn it into a token using oauth.OAuthToken? I've tried both
> CONSUMER_SECRET and GENERAL_SECRET and always get

We use "token" and "key" interchangeably.  Since the token corresponds
to a user who has authorized your app, you have their secret
somewhere.

> fireeagle_api.py", line 312, in fetch_response
> raise FireEagleException, msg
> fireeagle_api.FireEagleException: Invalid OAuth signature. (Code 23)
>
> The API explorer leads me to believe that no secret is passed, but the
> terminology is really quite confused - OAuth calls it a key, but FE calls it
> a secret, usually, but even FE can't keep it straight when discussing
> CONSUMER vs GENERAL ...

No secret is ever passed.  However, you do have to create appropriate
OAuth signatures with the correct secrets.

Can you point me at the docs that are confusing and I'll see what I
can do about clarifying them?

> What's the right way to use the GENERAL_TOKEN?

As a substitute to a user's access token when calling /recent,
/within, or /lookup (which will also work with access tokens).

> My idea is that there will be a server process that uses /recent to
> watch changes in the location of users. It's not clear to me how that
> server process needs to authenticate to FE - the /recent
> documentation indicates that it should use the General Purpose
> token and secret ... is it that simple? Just pass in the token with the
> call, or does there need to be an exchange at startup? That's question 1.

No exchange.  General Purpose tokens are granted when you create your
app and are used when you want your application to "act on its own
behalf".  (Where using access tokens allow you to "act on a user's
behalf".)

> The other question regards user authentication. I'd like to piggyback
> on the existing FE authentication/authorization mechanism to avoid
> building my own user/password system - I have some RESTful APIs
> that allow users to set up the notification actions they're interested,
> and I'd be happy to have them (somehow) authenticate via FE/Yahoo
> and then come back to my APIs. I know that I'm waving my hands
> furiously here, because I don't quite understand what's going on under
> the covers when someone authenticates to FE ... but perhaps
> someone will clear it up a bit for me?

BBAuth (Y!'s Single-Sign-On solution) might help you out here:
http://developer.yahoo.com/auth/

Having a user authorize your application to read their location is a
way for you to provide credentials to Fire Eagle that we can recognize
without sending a username/password over the wire.  It also allows us
to refer a user with an opaque identifier that has no meaning to us.
However, said opaque identifier will have meaning to your application,
as it will be tied to their "account" on your system.  The result is
that we can both refer to the same "user" using a shared identifier
that means different things to both sides.

(wikinear.com is an example of an application that doesn't include a
notion of "users"; credentials are stored in a browser's cookies and
tie that browser instance to a user's Fire Eagle location.)

I hope this helps.

seth

I'm glad to see that you've been making progress.  If you'd like to
         receive updates in real-time, you can try out our XMPP pubsub node
         (which hasn't been documented yet).  There are Ruby-focused docs and
         libs here:
         http://github.com/mojodna/fire-hydrant/tree/master

Seth, that will be very cool, indeed ... but I'd like to figure this out, too,
because I'm still finding the auth process confusing.

         You'll have to make a second request back to /user w/ the access token
         and secret that correspond to the token you want the location for.
         (This is all about limiting exposure should certain keys/secrets leak
         out.)

OK, that makes sense, but it's not what I expect from the API explorer which
returns a location. Maybe that's because I'm doing it as myself?

         We use "token" and "key" interchangeably.  Since the token corresponds
         to a user who has authorized your app, you have their secret
         somewhere.

The problem with using "token" in this way is that it's easy to confuse with an
OAuth token, which is a different thing, and is sometimes what is needed in the
API call.

I have their secret? Really? Maybe I was supposed to save something that I
didn't :-)


         No secret is ever passed.  However, you do have to create appropriate
         OAuth signatures with the correct secrets.

Yes, of course. But the only secrets that I know to pass in are either the
CONSUMER_SECRET or the GENERAL_SECRET. I didn't save the access (OAuth) token
that was returned when I authorized (I'm the only user right now). Is that the
secret I need? Easy to re-authorize and test...(fiddle fiddle fiddle) yes!
Woohoo!

         Can you point me at the docs that are confusing and I'll see what I
         can do about clarifying them?
       ...

         > What's the right way to use the GENERAL_TOKEN?

         As a substitute to a user's access token when calling /recent,
         /within, or /lookup (which will also work with access tokens).

Well, right there we've got confusion. The /recent call needs an OAuth token,
and the GENERAL_TOKEN is not such a thing.

(And the mechanism for using the returned data from /recent could use more
documentation, too! And it appears that the default return from /recent doesn't
have much of a time limit, unlike what the doc says for the default.)

         BBAuth (Y!'s Single-Sign-On solution) might help you out here:
         http://developer.yahoo.com/auth/

         ...

         I hope this helps.

Yes, thanks. It's starting to make more sense.... slowly.

The download links at

http://github.com/SteveMarshall/fire-eagle-python-binding/tree/master/fireeagle_\
api.py

appear to be busted.