qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adel Boutros <Adelbout...@live.com>
Subject Re: Heads-up: Splitting proton-c into multiple libraries [Was: Proton's road ahead]
Date Mon, 14 Nov 2016 13:04:44 GMT
Hello,


What are the impact of these changes from a user point of view? Will the upgrade be automatic
or will it require changes as was the case with the update from 0.12 to 0.14 for example?


Regards,

Adel

________________________________
From: Andrew Stitcher <astitcher@redhat.com>
Sent: Friday, November 11, 2016 9:41:37 PM
To: users@qpid.apache.org
Subject: Re: Heads-up: Splitting proton-c into multiple libraries [Was: Proton's road ahead]

We could certainly copy the URL parser functionality into the C++
binding but as Ken notes it is used in the reactor so we'd have to
leave it there too (although we can make it private).

As for the parser for the pn_data_t I think that can be completely
removed as I'm not aware of any use of it all.

Andrew


On Fri, 2016-11-11 at 15:25 -0500, Ken Giusti wrote:
> IIRC C reactor also uses the url parser.
>
>
> ----- Original Message -----
> >
> > From: "Justin Ross" <justin.ross@gmail.com>
> > To: users@qpid.apache.org
> > Sent: Friday, November 11, 2016 3:02:40 PM
> > Subject: Re: Heads-up: Splitting proton-c into multiple libraries
> > [Was: Proton's road ahead]
> >
> > On Fri, Nov 11, 2016 at 8:46 AM, Andrew Stitcher <astitcher@redhat.
> > com>
> > wrote:
> > >
> > >
> > > Extra (potential) library: All source in directory
> > > - extra
> > >
> >
> > Could we avoid having this extra library if we copied the URL
> > parser to the
> > C++ binding?  You noted elsewhere that the only other thing in
> > here, the
> > data parser, isn't currently used.
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message