0004668: sources naming

ID	Project	Category	View Status	Date Submitted	Last Update
0004668	Taler	exchange	public	2016-09-20 14:28	2016-10-11 15:28

Reporter	Marcello Stanisci	Assigned To	Christian Grothoff	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	none	Severity	tweak	Reproducibility	have not tried
Status	closed	Resolution	won't fix
Product Version	0.0
Target Version	0.1	Fixed in Version	0.1

Summary	0004668: sources naming
Description	The exchange codebase contains at least two source file whose code does not match the intuitive domain given in filename. For example, no function in exchangedb/exchangedb_denomkeys.c fetches data from the DB, just from disk (via filesystem). The same holds for exchangedb_signkeys.c. Unless here "db" means also "from filesystem", this naming is a bit misleading.
Tags	No tags attached.

Date Modified	Username	Field	Change
2016-09-20 14:28	Marcello Stanisci	New Issue
2016-09-20 14:28	Marcello Stanisci	Status	new => assigned
2016-09-20 14:28	Marcello Stanisci	Assigned To	=> Christian Grothoff
2016-09-20 14:47	Christian Grothoff	Note Added: 0011130
2016-09-20 14:48	Christian Grothoff	Status	assigned => informing
2016-09-20 14:48	Christian Grothoff	Resolution	open => won't fix
2016-09-20 14:48	Christian Grothoff	Fixed in Version	=> 0.1
2016-09-20 14:48	Christian Grothoff	Target Version	=> 0.1
2016-10-11 15:28	Christian Grothoff	Status	informing => closed

Christian Grothoff 2016-09-20 14:47 manager ~0011130	Files on disk can be considered a "database", this is an implementation detail. For the rest of the code, what matters is that this is some type of persistent storage, so "db" is fine. I think you're reading too much into the name here.