> On Jul 26, 2019, at 17:31, Walt Karas wrote:
>
> That will break current plugins so I wait for more input before I proceed.
That’s ok between major versions, and a trivial code change . But yes, should
be vetted here.
— Leif
>
>
>> On Fri, Jul 26, 2019 at 4:15 PM Leif Hedstrom wrote:
That will break current plugins so I wait for more input before I proceed.
On Fri, Jul 26, 2019 at 4:15 PM Leif Hedstrom wrote:
> Hmm we have APIs to get the VC no? If so, I think we should only have the
> lowest level API, and avoid duplicating functionality.
>
> I’m fine deprecating / removin
Hmm we have APIs to get the VC no? If so, I think we should only have the
lowest level API, and avoid duplicating functionality.
I’m fine deprecating / removing any obsoleted APIs in favor of a new, more
generic one.
— Leif
> On Jul 26, 2019, at 16:14, Alan Carroll
> wrote:
>
> Ah, I tho
Ah, I thought you were asking if that could be removed. Yes, if it's not
there already, it seems like a good addition.
On Fri, Jul 26, 2019 at 11:05 AM Walt Karas
wrote:
> There are API functions to determine in a transaction or a session are
> internally-created. They look at their client-side
There are API functions to determine in a transaction or a session are
internally-created. They look at their client-side VConn, and see if it's
internally-generated. But there is currently no API function that takes a
TSVConn parameter and returns whether or not it is internally-created.
On Thu
