The "Common formats" include simple representations like JSON, XML, or CSV, but also include database writing/retrieval formats. For example, one "format" interfaces with MySQL databases. The premise behind the library is not just data conversions, but basically an ETL implementation that provides analysis filters on the data as well. If the internal representation is not used, there is practically no limit to the size of data being converted or analyzed. This is a major difference from Boost.Serialization. On 01/09/2018 12:45 PM, Edward Diener via Boost wrote:
On 1/9/2018 12:36 PM, Oliver Adams via Boost wrote:
Hi all,
I was wondering if a library I'm developing would be of value to the Boost community. It is basically an event-driven parsing/serialization library for common formats using a standard internal representation or simple pass-through conversions. Would anyone be interested in something like this being added to Boost?
Thanks.
"Common formats" needs to be specified. Boost already has a serialization library so you might also want to explain how your library is different from that. It is always a good idea to be as specific as possible when querying about the interest in a new library.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost