#Documentation about web architecture and goal for version 4 release.

1) main goals for version 4 release
* A new install with graphical interface ok
* A graphical tools to build his own package easily
* Compilation result as tar.gz of src.rpm, compiled package, source.tar.gz ans specs file generated.


2) Priority reorder - declassed goals for release 4
	* A web interface allowing user to build rpm on the local machine

* Full template abstraction from rpm way

2) 2 main pages

2.1) Package information
Package information are stored in session.

First part of the GUI: Package meta data
1R Package Name
2R Package Version
3R Package Release
4A Package Description
5A Package Summary

Second part of the GUI : Archive file
7R Archive File
8A User name for the archive
9A Group name for the archive
10A Exclude some file patterns

Third part : build information
6R Split into several packages: config, doc et main
13A Requires
14A Build script
15A Pre install script
16A Post install script
17A Pre uninstall script
18A Post uninstall script
 
Fourth part : template inforamtion
11R Template used
12A Template upload


2.2) Packager information
Packager information are stored in Cookies so that no more extra information need to be store on the server.

What kind of information is stored about it ?

* Packager First Name
* Packager Last Name
* Packager Vendor
* Packager Url Vendor


Rpm Build Processus :
	* a request is post

	* a lock file is set to avoid multi post of the same package

	* a folder is created with uniqid

	* tar is write in this folder
	
	* a XML/TCP request is send to indicate a new package to build

	* a server receives a place treatment into fifo

	* build package a place result in the uniqid folder

	* send a mail to the packager to tell him this package is ready
	
	* lock file is removed in lock folder