=2D--------- Forwarded Message ----------
Subject: Re: Synchorized WEB akregator
Date: Friday 11 March 2005 23:54
=46rom: S=E9bastien Lao=FBt <slaout@...>
To: Frank Osterfeld <frank.osterfeld@...>
> We are improving the feed archive right now, abstracting from the actual
> storage backend. So it should be possible in the future to use e.g. an SQL
Yes, I've seen.
Very good (especially for the responsivness and startup times, even if
it's not the suject of this mail ;) Good thing).
> What kind of architecture would you suggest (I ask as I have zero
> experience in developing web apps)?
I'm developing with PHP language.
I think I would do it with PHP.
Even if it's not clean (a better way would be to make a server program
to upload to a server).
More informations below.
Basically akregator would have those new methods:
=2D getFeedsList(username, password, sinceDate);
Send back to akregator the feeds added by the user on the web frontend
(or from another akregator, of course) since last update (so, no need
to retreive all the feeds everytimes akregator startup.
=2D getReedsNews(username, password, feedId, sinceDate);
Let akregator update the read status for reads at work news.
=2D setReedNews(username, password, feedId, newsId);
When user in akregator read a feed, it send back to the server the id
of the news, so it's read on the wbe frontend too...
And so on (not thinked to it yet)...
Those akregator methods would make HTTP requests to the server, eg.
K675FGJ&sinceDate=3D2006-01-31 The server side PHP script /synch/index.php =
process data (look in a database...) and send the newly added feeds back to
akregator in plain text...
Was this such informations you asked by "architecture"?
Concerning the WEB frontend, no problem: it's like I already done, or
any PHP developer can do.
> Sounds interesting, what kind of program? (I hope not another aggregator
Nope. Be rassured ;)
That's basically an advanced notes taking program:
http://basket.kde.org/ (the initial KDE program)
http://basket.kde.org/w/new_user.php (in progress WEB interface)
=46or the moment it's only a WEB interface (not finished, not yet
released) done with PHP.
The app and the web app aren't synchronized yet.
So, technical details:
I'm doing the WEB frontend in PHP. That's OK.
=46or the BasKet<->WeBasKet_server connections I think I will implement
this in PHP too.
eg. when BasKet need to talk with WeBasKet it send an HTTP request to
WeBasKet server that reply with a HTTP reply.
It would work on the port 80, so it can pass firewalls (if it was a
server program it would be obliged to use another port I can't access
from my work, for instance).
It's also better so that people could install the PHP script on his
server, even if it's a free server (lycos...): no need to install a
program on the server, so it's OK.
Why? Because I'm myself hosted by a sort of free host (although I could
install such server deamons). And my program will certainly have a lot
of users, which will generate a lot of traffic.
And I don't want to abuse of the host.
So, by facilitating WeBasKet servers installation it allow to move some
traffic on other sites.
I don't know if you thinked about what server would host a possible
"project codenamed WebAkregator" ;) ?
Would your current server be OK?
I haven't yet (and don't know how to) estimated the load of clients
calling server every 10 minutes to know if there is something new.
The server database should also be available for web frontend but also
for the "synchronizer" between akregator<->webAkregator.
> I think that would be definitely a valuable goal. The backend part should
> be doable - but I doubt we have the man-power to develop and maintain a w=
> frontend, as we are only a small team and there are many things (the next
> time it'd will be mostly refactoring) on the agenda. So it would be good =
> someone else would join (hint, hint ;) ) and code the web frontend as soon
> the backend stuff is sorted out and stable API-wise.
Are you pointing me to do the web frontend? :)
Heu... No, I don't think I would have time too.
Of course, since I will do such a same project I could share PHP classes
and so... as a start for you.
Currently, I'm alone on my project. It's why it's developed so slowly.
And I have a lot of new things to add to the KDE app before I can start
the synchronization work.
So I'm afraid I willn't do it in 2005 :(
Of course I would like to do the akregator web interface (because I need
it quite quickly).
Perhapse I could begin by the WebAkregator... I think it would be
simplier than my prog, but what are you planning to do with akregator
that would need un update of the web frontend?
ie. if I do a simple frontend that just maintain feeds list and allow to
view news... are there any new concepts that would be introduced in
akregator and that should be added to the web frontend?
PS: Have this mail been forwarded to other akregator developers?
Or is there a need for a wiki page?
Or is there a mailing list I can post to?
PS2: Sorry for this long mail!