Now this could "user" issue, but I've been looking at the xmlGuide api and trying to figure out better ways to download and manage the data.
I run into a small problem downloading a full days guide (7mb) so I thought I might try and reduce the size by requesting slices of the day (this is also an effort to speed up the xml parsing routines...but that's another story).
My inital request was: (midnight 25/8 to midnight 26/8 - I had been playing around with using 23:59:59:99 as the last time, but this generally gives back the same result anyway)
http://iceguide.icetv.com.au/cgi-bin/epg/iceguide.cgi?op=xmlguide&start_date=090825000000&end_date=090826000000
I then thought I'd only grab a 4 hour window:
http://iceguide.icetv.com.au/cgi-bin/epg/iceguide.cgi?op=xmlguide&start_date=0908250000&end_date=0908250400
But this to downloaded the "whole" days guide (all 7mb) as well??
Any ideas??
Shane
I run into a small problem downloading a full days guide (7mb) so I thought I might try and reduce the size by requesting slices of the day (this is also an effort to speed up the xml parsing routines...but that's another story).
My inital request was: (midnight 25/8 to midnight 26/8 - I had been playing around with using 23:59:59:99 as the last time, but this generally gives back the same result anyway)
http://iceguide.icetv.com.au/cgi-bin/epg/iceguide.cgi?op=xmlguide&start_date=090825000000&end_date=090826000000
I then thought I'd only grab a 4 hour window:
http://iceguide.icetv.com.au/cgi-bin/epg/iceguide.cgi?op=xmlguide&start_date=0908250000&end_date=0908250400
But this to downloaded the "whole" days guide (all 7mb) as well??
Any ideas??
Shane