Skip to content

Fixed typographical error, changed aquisition to acquisition in README. #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
orthographic-pedant wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed typographical error, changed aquisition to acquisition in README. #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
Configuration abstraction framework using Google Protocol Buffers, Spring and varous formatters
# Concepts
Configuration framework is designed to provide separation between config consumption and aquisition. The `consumer` package provides interfaces that should be coded against by the application wishing to consume the config data. The data is returned in the form of Google Protocol Buffers `Message` objects which have been populated from various dedicated or augmenting sources (HTTP, Files, DB, etc) stored in various formats (XML, JSON, Properties, Protobuf Binary, etc). The `provider` package provides interfaces that should be coded against by the config data retrieval providers and formatters. The responsibility of actually interpreting the `ConfigParam` elements and deciding on where to load the actual config data from and what format conversion to use falls upon the jurisdiction of `ConfigProvider` implementations.
Configuration framework is designed to provide separation between config consumption and acquisition. The `consumer` package provides interfaces that should be coded against by the application wishing to consume the config data. The data is returned in the form of Google Protocol Buffers `Message` objects which have been populated from various dedicated or augmenting sources (HTTP, Files, DB, etc) stored in various formats (XML, JSON, Properties, Protobuf Binary, etc). The `provider` package provides interfaces that should be coded against by the config data retrieval providers and formatters. The responsibility of actually interpreting the `ConfigParam` elements and deciding on where to load the actual config data from and what format conversion to use falls upon the jurisdiction of `ConfigProvider` implementations.

# Formats
The framework uses [Protobuf Java Format](http://code.google.com/p/protobuf-java-format/) library for converting XML, JSON, Text and Properties files into Protocol Buffers Messages. `AbstractConfigProvider` provides a `convertMessage` function that is handling the conversion from the above-mentioned formats.
Expand Down