gnuherds-app-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DB vs FS based webapp architectures -- web 2.0 -- RSS, etc.


From: Davi Leal
Subject: Re: DB vs FS based webapp architectures -- web 2.0 -- RSS, etc.
Date: Thu, 8 May 2008 22:51:00 +0200
User-agent: KMail/1.9.7

Antenore Gatta wrote:
> Hey guys, correct me if I'm wrong, you are both right, but you are speaking
> about two completely different platforms.
>
> Both they work and both, if well implemented, they work well.

IMHO we are speaking about two different webapp architectures.

My position is that a file storage based architecture will be more complex to 
develop and maintain than the current relational database based one.



> The question is if we want to move to web 2.0 technologies or not.

IMHO "web 2.0" is not a technology but a way to use the web technologies with 
the goal of "enhance collaboration among users".

  http://en.wikipedia.org/wiki/Web_2.0

The current gnuherds.org webapp is a "web 1.0" webapp because it does not 
allow for example a user defining an offer and other users adding her own 
modifications to the same offer, to end with an offer created collaboratively 
by a set of webapp users.  That is how wikis work.

When the micro-payments feature be ready the project will be able to allow a 
set of users contributing to pay the same offer;  For example, I will 
contribute 2 EURs, you will contribute 1 EUR, ... all to get an offer which 
will pay 3000 EURs to develop for example a new Linux graphic driver.


> IMHO we should think about that possibility but in a second (third
> actually) phase and to think well how to do it.

I agree about follow developing the project by phases, according to the human 
resources availables at each time to contribute.

> I strongly advice to keep the actual architecture, that works, and improve
> it maybe adding some web 2.0 features time by time (feeds, syndications,
> export in RSS, atom, and so forth), playing with them and in the mean while
> think about a future new version.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]