I had a side conversation with John. I created a proposal in a separate and
a JIRA (GEODE-7555) for what I think is a good long term solution to the
issues STDG had mocking the Geode API.
In the short term, I'm fine with whatever we decide we should do to support
STDG.
-Dan
On Thu, Dec 5, 2019 a
+1
To the extent possible without breaking existing APIs, please name the new
stuff to indicate what’s in the pool (E.g. ConnectionPool,
ConnectionPoolService, and so on).
—
Dale Emery
dem...@pivotal.io
> On Dec 5, 2019, at 4:40 PM, Dan Smith wrote:
>
> Hi,
>
> I wrote up a proposal for d
Hi,
I wrote up a proposal for deprecating of the singleton PoolManager in favor
of a ClientCache scoped service. Please review and comment on the below
proposal.
I think this should address the issues that Spring Data Geode and friends
had trying to mock Pools and remove the need for those projec
Trying to get a conclusion out of it:
- The SDG/STDG to address the issue by changing the code on its part
- Create JIRA ticket for the issue raised. And prioritize/work the issue in
coming GEODE release.
-Anil.
On Thu, Dec 5, 2019 at 10:12 AM Owen Nichols wrote:
> > On Dec 4, 2019, at 10:09 P
> On Dec 4, 2019, at 10:09 PM, Jacob Barrett wrote:
>
> I think we can tone down the inflammatory statements
Jake, thank you for speaking up, I felt the same way but wasn’t sure how to say
it.
This might be a good opportunity for all of us to review the
https://cwiki.apache.org/confluence/dis
+1 to what Jake said.
-Dan
On Wed, Dec 4, 2019 at 11:32 PM Owen Nichols wrote:
> +1 for a short-term solution in 1.11 while we discuss a more complete
> proposal for 1.12
>
> On Wed, Dec 4, 2019 at 10:09 PM Jacob Barrett wrote:
>
> > I think we can tone down the inflammatory statements. It is
Diffie-Hellman is a valid and in-use protocol by the larger security
community.
On Thu, Dec 5, 2019 at 8:24 AM Blake Bender wrote:
> Please see https://issues.apache.org/jira/browse/GEODE-7302. We have a
> ticket to make a decision about whether or not to deprecate a couple of
> properties here
Please see https://issues.apache.org/jira/browse/GEODE-7302. We have a
ticket to make a decision about whether or not to deprecate a couple of
properties here, and any knowledge of them has long since left the team.
Does anyone have a clue, or informed opinion, as to the importance of
keeping this
Thanks Charlie, but the issue is not about connectivity. Summarizing the issue,
the problem is that if you have two or more gw receivers that are started with
the same value of "hostname-for-senders", "start-port" and "end-port" (being
"start-port" and "end-port" equal) parameters, if one gw rec
