i have to agree with YoLoLo. maybe release the new version with WinInet in a shorter time and keep developing your implementation. Regards Joel -----Original Message----- From: yololo@xxxxxxxxxxxxxxx To: prssr-devel-ml@xxxxxxxxxxxxx Date: Wed, 23 Nov 2005 07:17:33 +0100 Subject: [prssr-devel-ml] Re: Updating feeds > Hi all, > > Well, to me , it depends on when you want to release the 1.1.5 final > version... > Very soon : Use the standard tool, and keep your work for a future > implementation (but i've got some feeds, and i have to refresh 2 times > to have the entire feeds) > Not in a hurry : Then, we got homework ! Another cycle of beta > testing... We are here to help ! > > Best regards > YoLoLo > > > ----Message d'origine---- > >Date: Wed, 23 Nov 2005 01:45:02 +0100 > >De: David Andrs <pda@xxxxxxxxxxxxx> > >A: prssr-devel-ml@xxxxxxxxxxxxx > >Sujet: [prssr-devel-ml] Updating feeds > > > >Hi to all beta testers! > > > >Last two weeks I was dealing with updating feeds. There are two major > problems: > >a) updating is slow > >b) updating is not reliabe > > > >For testing I have used Hal's OPML file (over 60 feeds) - very good > >for testing. The current implementation of download/update is done via > >WinInet API. It is very easy to use, but very slow. > > > >So I tried to replace this API with my own. I succeeded. The result > is: > >- 4x times quicker update > >- pRSSreader is about 3KB larger > > > >But there are some problems. If I used Hal's test file, about 10 feeds > >was updated sucessfully, the rest was not. Not good. So I tried to > >figure out where is the problem. > > > >I tried similar implemetation with WinInet then with MFC wrapper of > >WinInet. The former one had similar result as my own implemetation, > >the latter one was a bit more successful. Every updates were run with > >cradled PDA and connection via ActiveSync on desktop PC. > > > >On monday I tried my own implementation on WiFi connection and it runs > >perfectly - fast and reliable. I have made test with Egress, if it is > >able to update Hal's OPML file and the result was pretty same as with > >pRSSreader. Thus, there must be some error in ActiveSync which > >disallows a lot of subsequent connections, because if I updated site > >by site manually (not via Update All), the reliability grows up > >(nearly 100%). > > > >Now, I have to make decision which implementation should I use and I > >would like to know your opinions. Here are pros (+) and cons (-): > > > >WinInet: > >+ quite reliable with ActiveSync > >+ smaller pRSSreader's binary > >+ debugged > >- slow > >- hard to extent in future (SSL, digest authentication), but probably > possible > > > >My implementation: > >+ fast > >+ easy to extent > >+ quite reliable with ActiveSync > >+ full control on what is happening > >- bigger pRSSreader's binary > >- not full implementation of HTTP - will need lot of tests to work > >properly (will need your help) > > > >-- > >David > >-- > >pRSSreader development mailing list > >prssr-devel-ml@xxxxxxxxxxxxx > >//www.freelists.org/archives/prssr-devel-ml > > > > ------------------------------------------------------------- > NetCourrier, votre bureau virtuel sur Internet : Mail, Agenda, Clubs, > Toolbar... > Web/Wap : www.netcourrier.com > Téléphone/Fax : 08 92 69 00 21 (0,34 ? TTC/min) > Minitel: 3615 NETCOURRIER (0,16 ? TTC/min) > > -- > pRSSreader development mailing list > prssr-devel-ml@xxxxxxxxxxxxx > //www.freelists.org/archives/prssr-devel-ml > > -- pRSSreader development mailing list prssr-devel-ml@xxxxxxxxxxxxx //www.freelists.org/archives/prssr-devel-ml