Web services and business rules engines
We have a web service that takes in input different types of messages. The function of the webservice is to merely write in a database the content of the messages. There is about one table (with foreign keys to others) for every kind of message.
User Configuration of a Shell Script. Best practices?
I am writing a shell script with a few variables that should be configured by the user. There will be an installer for downloading and configuring the script, possibly by asking a series of question. The script in question is aimed at other developers.
Where Should I Put Configuration Files?
I’m creating a project that I want to be able to distribute across platforms. I’m writing in Java and AWT which already gives me a pretty large range of devices, but I’m mostly interested in Windows and Linux (Debian/Ubuntu).
Configuration data: single-row table vs. name-value-pair table
Let’s say you write an application that can be configured by the user. For storing this “configuration data” into a database, two patterns are commonly used.
Minimize useless tweaking of a numeric app [closed]
Closed 9 years ago.
Is using something other than XML advisable for my configuration file?
I have a small tool I’m designing which would require a configuration file of some sort. The configuration file in my case is really more of a database, but it needs to be lightweight, and if needed the end-user should find it easily editable. However, it also will contain a lot of things in it. (depending on certain factors, could be 1Mb or more)
Is it appropriate to run a complex enterprise-system configuration and migration project in a similar way to a Scrum development project?
I’m just starting out on the implementation of a large enterprise-wide system, which has complex requirements and many stakeholders.
How to sell logistical procedures that require less time to perform but more finesse?
I am working with a group where part of the responsibilities is managing a certain set of configuration files which, of course, have the same skeleton/structure across different environments but different values (like server, user, this setting, that setting etc.). Pretty classic scenario…
Grouping classes by subject or dependencies?
Our project consists of user application and server application. The server application prepares data files that the user application consumes. Because the data is huge, it is stored in custom format. So the project includes many classes related to reading and writing the data. The user application does not need the writing side, so we don’t want to have the code there both because it might run on resource-limited devices and because it prolongs compilation (C++ is not known for having fast compilers).
Should I use a config file or database for storing business rules?
I have recently been reading The Pragmatic Programmer which states that: