full stats page VS widget (& curl vs WP HTTP api)

[futtta]

hi group;
from what I see this plugin generates a widget on the dashboard, but
can it also create an admin page with "live" info on what happens
today (most popular posts, referrers, search terms, ..., much like the
wp.com stats report page does)? is this something that is planned/
might be considered?

2nd question: the plugin uses CURL natively, whereas wordpress has a
full-fledged HTTP API (cfr. http://codex.wordpress.org/HTTP_API) in
place that provides a generic way to do http (with support for a
proxy). using that API instead of CURL might simplify the code & would
leave low-level implementation details (including the choice between
fopen, fsockopen, curl, ...) to the API?

kind regards,
frank

[Carson]

Yes, I just haven't had time to do it yet or anyone say what they
would like to see in the stats. Don't forget that it is only as up to
date as what is in Google Analytics so it wouldn't really be "live"
but I could allow for shortening the window from a month down to week/
day/etc. Is that what you are looking for? I haven't looked at wp.com
stats in a long while so maybe I should look at that. I was also going
to integrate other sources into the stats as well as add support for
some of the newer stats available in Google Analytics.

I will look at the http api. I think the biggest hurdle is support for
setting request headers and it looks like that isn't documented on the
page but that it can be done. It would definitely make it easier for
some so I'll give it a shot. I'll have to verify that it works
correctly even when it drops down to one of the non-curl apis.

On Mar 18, 8:42 am, futtta <fut...@gmail.com> wrote:
> hi group;
> from what I see this plugin generates a widget on the dashboard, but
> can it also create an admin page with "live" info on what happens
> today (most popular posts, referrers, search terms, ..., much like the
> wp.com stats report page does)? is this something that is planned/
> might be considered?
>
> 2nd question: the plugin uses CURL natively, whereas wordpress has a

> full-fledged HTTP API (cfr.http://codex.wordpress.org/HTTP_API) in