[RVI] configuration file format

Sanjeev B.A. iamsanjeev at gmail.com
Mon Aug 1 12:10:11 EDT 2016


I have observed (in other projects) that these config files  grow to
support more features and flexibility, over time.
JSON seems like a good choice to me.
(https://github.com/DaveGamble/cJSON)


On Tue, Aug 2, 2016 at 12:54 AM, Feuer, Magnus <mfeuer1 at jaguarlandrover.com>
wrote:

> Maybe http://zserge.com/jsmn.html ?
>
> Has JSON parsing, but is also encompassing enough to handle simple key:
> value pairs.
>
> If we need to use a tree structure for our RVI Library config data, then
> JSON is probably the best way to go. However, if a flat structure will do
> it for us, JSON will just add complexity without value.
>
> Seems like JSMN will keep both options open for us, though.
>
>
> /Magnus F.
>
>
>
> -------------------
>
> *Head System Architect - Open Source Projects**Jaguar Land Rover*
>
> *Email*: mfeuer1 at jaguarlandrover.com
> *Mobile*: +1 949 294 7871
>
>
>
> Jaguar Land Rover North America, LLC
> 1419 NW 14th Ave, Portland, OR 97209
> -------------------
> Business Details:
> Jaguar Land Rover Limited
> Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
> Registered in England No: 1672070
>
> This e-mail and any attachments contain confidential information for a
> specific individual and purpose.  The information is private and privileged
> and intended solely for the use of the individual to whom it is addressed.
> If you are not the intended recipient, please e-mail us immediately.  We
> apologise for any inconvenience caused but you are hereby notified that any
> disclosure, copying or distribution or the taking of any action in reliance
> on the information contained herein is strictly prohibited.
>
> This e-mail does not constitute an order for goods or services unless
> accompanied by an official purchase order.
>
> On Fri, Jul 29, 2016 at 6:12 PM, Jeremiah Foster <
> jeremiah.foster at pelagicore.com> wrote:
>
>> On Jul 29, 2016 6:05 PM, "Streif, Rudolf" <rstreif at jaguarlandrover.com>
>> wrote:
>> >
>> > For what's worth it, I personally never cared for the INI file format
>> as it is too easy to miss a section and mess it up in longer files. It's
>> also more effort to parse it.
>> >
>> > For simple configuration with a pseudo hierarchy I prefer:
>> >
>> > path.to.property.0 = value0
>> > path.to.property.1 = value1
>> >
>> > It's easy to parse and can be used in a tree.
>> >
>> > If it needs more flexibility and lists, dicts etc. I would use JSON.
>>
>> +1
>>
>> FWIW GENIVI uses JSON in a couple of other projects.
>>
>> Regards,
>>
>> Jeremiah
>>
>> >
>> > Cheers,
>> > Rudi
>> >
>> > On Fri, Jul 29, 2016 at 2:03 PM, Jamison, Tatiana <
>> tjamison at jaguarlandrover.com> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> For the client implementation of RVI in C, the user will specify a
>> configuration file in the calling application. This configuration file will
>> specify the location of device certificate and key, the trusted certificate
>> store, RVI credentials, and addresses of remote nodes to connect to on
>> startup (if any).
>> >>
>> >> Any strong opinions on the format of this file? I'm thinking INI style
>> (also used by OpenSSL), with a structure like:
>> >>
>> >> [section0]
>> >> property0 = value0
>> >> property1 = value1
>> >> ...
>> >>
>> >> --
>> >> Tatiana Jamison
>> >> Software Developer
>> >>
>> >> Jaguar Land Rover North America, LLC
>> >> 1419 NW 14th Ave. Portland. OR 97209
>> >> JaguarUSA.com  |  LandRoverUSA.com
>> >
>> >
>> >
>> >
>> > --
>> > Rudolf J Streif
>> > System Architect - Open Source Initiative
>> > Open Source Technology Centre
>> >
>> > M: +1.619.631.5383
>> > Email:  rstreif at jaguarlandrover.com
>> >
>> >
>> >
>> > UK: G/26/2 G02 Building 523, Engineering Centre, Gaydon, Warwick, CV35
>> ORR
>> > US: 1419 NW 14th Ave, Portland, OR 97209
>> > jaguar.com | landrover.com
>> > -------------------
>> > Business Details:
>> > Jaguar Land Rover Limited
>> > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
>> > Registered in England No: 1672070
>> >
>> > This e-mail and any attachments contain confidential information for a
>> specific individual and purpose.  The information is private and privileged
>> and intended solely for the use of the individual to whom it is addressed.
>> If you are not the intended recipient, please e-mail us immediately.  We
>> apologise for any inconvenience caused but you are hereby notified that any
>> disclosure, copying or distribution or the taking of any action in reliance
>> on the information contained herein is strictly prohibited.
>> >
>> > This e-mail does not constitute an order for goods or services unless
>> accompanied by an official purchase order.
>> >
>> >
>> > _______________________________________________
>> > genivi-projects mailing list
>> > genivi-projects at lists.genivi.org
>> > http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects
>> >
>>
>> _______________________________________________
>> genivi-projects mailing list
>> genivi-projects at lists.genivi.org
>> http://lists.genivi.org/cgi-bin/mailman/listinfo/genivi-projects
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-projects_lists.genivi.org/attachments/20160802/beeead8e/attachment.html>


More information about the genivi-projects mailing list