Martin Bjorklund writes:
> wrote:
>> Ladislav Lhotka writes:
>> > I think we need to eliminate all kinds of recursive mount, so this
>> > should not happen.
>>
>> While I think I need more help understanding the original problem (maybe
>> more explicit example of where the conflict is?), I want
wrote:
>
> Ladislav Lhotka writes:
>
> > Hi Anton,
> >
> > Anton Tkáčik writes:
> >
> >> Hi,
> >>
> >> if I understand correctly netmod-structural-mount inlines "mounted" data
> >> directly to container / list which is used,
> >>
> >> which brings up following issues:
> >>
> >>
> >> 1. It is
Ladislav Lhotka writes:
> Hi Anton,
>
> Anton Tkáčik writes:
>
>> Hi,
>>
>> if I understand correctly netmod-structural-mount inlines "mounted" data
>> directly to container / list which is used,
>>
>> which brings up following issues:
>>
>>
>> 1. It is possible to have identifier conflict bet
On Thu, Mar 24, 2016 at 02:47:33PM +0100, Ladislav Lhotka wrote:
>
> > On 24 Mar 2016, at 14:13, Juergen Schoenwaelder
> > wrote:
> >
> > On Thu, Mar 24, 2016 at 12:56:40PM +0100, Ladislav Lhotka wrote:
> >> Martin Bjorklund writes:
> >>
> >>> The fact that anydata can represent "really anyth
> On 24 Mar 2016, at 14:13, Juergen Schoenwaelder
> wrote:
>
> On Thu, Mar 24, 2016 at 12:56:40PM +0100, Ladislav Lhotka wrote:
>> Martin Bjorklund writes:
>>
>>> The fact that anydata can represent "really anything" does not mean
>>> that every server MUST allow the client to create "really
On Thu, Mar 24, 2016 at 12:56:40PM +0100, Ladislav Lhotka wrote:
> Martin Bjorklund writes:
>
> > The fact that anydata can represent "really anything" does not mean
> > that every server MUST allow the client to create "really anything"
> > for all anydata config nodes. It will depend on the se
Martin Bjorklund writes:
> Ladislav Lhotka wrote:
>> Hi Anton,
>>
>> Anton Tkáčik writes:
>>
>> > Hi,
>> >
>> > if I understand correctly netmod-structural-mount inlines "mounted" data
>> > directly to container / list which is used,
>> >
>> > which brings up following issues:
>> >
>> >
>> >
Ladislav Lhotka wrote:
> Hi Anton,
>
> Anton Tkáčik writes:
>
> > Hi,
> >
> > if I understand correctly netmod-structural-mount inlines "mounted" data
> > directly to container / list which is used,
> >
> > which brings up following issues:
> >
> >
> > 1. It is possible to have identifier conf
Hi Anton,
Anton Tkáčik writes:
> Hi,
>
> if I understand correctly netmod-structural-mount inlines "mounted" data
> directly to container / list which is used,
>
> which brings up following issues:
>
>
> 1. It is possible to have identifier conflict between data from model
> defining mount and
Hi,
if I understand correctly netmod-structural-mount inlines "mounted" data
directly to container / list which is used,
which brings up following issues:
1. It is possible to have identifier conflict between data from model defining
mount and mounted data (if mounted schema
contains same m
10 matches
Mail list logo
