initializing ding-libs with bytes (rather than with file)

[Yassir Elley]

Hi Dmitri,

When reading an INI file using SMB, the GPO code receives the data as an array of bytes. Once received, it writes the data to a local file, but only so that it can use the ini_config library to parse that local file. I would much prefer to just parse the bytes directly, without writing out the data to a local file. Can the ini_config library be initialized with a byte array, or can it only be initialized with a filename?

Regards,
Yassir.

[Dmitri Pal]

On 03/03/2014 04:41 PM, Yassir Elley wrote:
> Hi Dmitri,
>
> When reading an INI file using SMB, the GPO code receives the data as an array of bytes. Once received, it writes the data to a local file, but only so that it can use the ini_config library to parse that local file. I would much prefer to just parse the bytes directly, without writing out the data to a local file. Can the ini_config library be initialized with a byte array, or can it only be initialized with a filename?

File a ticket, I will have a look.
I think it would be a simple new call.
I however would create memory mapped file and read from it. This way I 
would be able to reuse most of the code. Would that approach work for you?
> Regards,
> Yassir.
> _______________________________________________
> sssd-devel mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/sssd-devel

[Yassir Elley]

----- Original Message -----
> On 03/03/2014 04:41 PM, Yassir Elley wrote:
> > Hi Dmitri,
> >
> > When reading an INI file using SMB, the GPO code receives the data as an
> > array of bytes. Once received, it writes the data to a local file, but
> > only so that it can use the ini_config library to parse that local file. I
> > would much prefer to just parse the bytes directly, without writing out
> > the data to a local file. Can the ini_config library be initialized with a
> > byte array, or can it only be initialized with a filename?
>
> File a ticket, I will have a look.
> I think it would be a simple new call.
> I however would create memory mapped file and read from it. This way I
> would be able to reuse most of the code. Would that approach work for you?

Ticket filed.
https://fedorahosted.org/sssd/ticket/2267

It think a non-persistent memory mapped approach sounds fine.

Thanks,
Yassir.