Update on new client/server protocol

Greetings, Geode friends. This is a summary of the progress in the development of the new client/server protocol. We’ve had some good input along the way and are getting close to an alpha release — exciting stuff! We’ve continued implementing Protobuf, now using it for serialization of primitive

Re: DISCUSS : Monitor the neighbour JVM using neihbour's member-timeout (GEODE-3411)

Hi, Aravind. Can you help me understand why this might be a useful feature for Geode? I see that your needs require it, but why would users in general want to allow longer timeouts for some members? This is a significant change with backward-compatibility implications, so would be good for the c

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

In this case, won't we be changing the default of this property with the next major release? So perhaps the choice is to follow the default=false convention now, or with the next major release..? On Wed, Sep 6, 2017 at 8:47 AM, Bruce Schuchardt wrote: > > > > On Sept. 5, 2017, 5:09 p.m., Galen

Re: Review Request 62088: GEODE-3249 Validate internal client/server messages

Ah, I see. Makes sense. On Sep 6, 2017 12:23 PM, "Bruce Schuchardt" wrote: I think we will want to remove this property in the next major release and have the behavior it enables be how the servers always act. On 9/6/17 10:23 AM, Brian Baynes wrote: In this case, won't we

New client/server protocol - seeking feedback

Greetings, friends of Geode. Work has been progressing on the new client/server protocol for Geode and we're approaching a GA v1.0. Completed work/features include put/get, putAll, getAll, remove, one-way SSL, authentication and authorization, and support for primitive types and JSON documents as

Re: New client/server protocol - seeking feedback

wrote: What's the best place to look for more details on the specific protocol for the v1.0 messages? The other pages on https://cwiki.apache.org/ confluence/display/GEODE/New+Client+Server+Protocol? Or directly in the code somewhere? -Dan On Fri, Sep 15, 2017 at 11:15 AM, Brian Baynes w

Re: []DISCUSS] Using package names to identify public API's

Yep, GEODE-3473 will make it in -- have been waiting for a good moment when there aren't other items in flight that would need to be rebased. On Fri, Sep 22, 2017 at 2:31 PM, Dan Smith wrote: > I found bug GEODE-3473 which was created based on this discussion. I marked > that as requiring a fix

Re: New client/server protocol - seeking feedback

data on the wire. I"m not sure if it's worth > complexity for this new protocol or not. > > Looking forward to seeing some more information about how to actually use > these messages to communicate with a server - IE what type of connection > should I create, how SSL wo

Re: 1.3.0 release

I've removed the 1.3.0 tag from these items: GEODE-3563 SSL socket handling problems in TCPConduit run GEODE-3705 New client protocol: Implement handshake GEODE-3637

Re: Starter tickets

+1 on starter/starter++ It will be nice to already have a group of possibilities to point folks to. On Mar 2, 2018 2:26 PM, "Kirk Lund" wrote: +1 for using starter and starter++ On Fri, Mar 2, 2018 at 1:45 PM, Joey McAllister wrote: > +1 to "starter" over "newbie." I think the ++ plan make

Request for edit permissions

Hello, I'm a new PM at Pivotal working with the Communications team. I'd like to request edit access for wikis and Jira tickets for Geode. For example, I'd like to edit the description for GEODE-2580, a project our team is working on. Thanks, Brian Baynes

Re: Request for edit permissions

t 8:32 AM, Brian Baynes wrote: > > Hello, > > > > I'm a new PM at Pivotal working with the Communications team. > > Quick note on the Apache way of doing things. While we appreciate > knowing your relationship with Pivotal please realize that neither your > tit

Re: Request for edit permissions

Thank you! On Mar 30, 2017 3:49 PM, "Roman Shaposhnik" wrote: > Done! > > On Thu, Mar 30, 2017 at 9:08 AM, Brian Baynes wrote: > > Hi, Roman. > > > > Sure, understood -- that info was by way of introduction, not a claim to > > anything :) > >

[jira] [Created] (GEODE-2940) Remove verification of locator host on start

Brian Baynes created GEODE-2940: --- Summary: Remove verification of locator host on start Key: GEODE-2940 URL: https://issues.apache.org/jira/browse/GEODE-2940 Project: Geode Issue Type: Bug

[jira] [Updated] (GEODE-2940) Remove verification of locator host on start

[ https://issues.apache.org/jira/browse/GEODE-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2940: Issue Type: New Feature (was: Bug) > Remove verification of locator host on st

[jira] [Created] (GEODE-2978) Add feature toggle for new protocol & merge into develop

Brian Baynes created GEODE-2978: --- Summary: Add feature toggle for new protocol & merge into develop Key: GEODE-2978 URL: https://issues.apache.org/jira/browse/GEODE-2978 Project: Geode I

[jira] [Created] (GEODE-2995) Introduce new protocol flow into core

Brian Baynes created GEODE-2995: --- Summary: Introduce new protocol flow into core Key: GEODE-2995 URL: https://issues.apache.org/jira/browse/GEODE-2995 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2996) New flow: put/get

Brian Baynes created GEODE-2996: --- Summary: New flow: put/get Key: GEODE-2996 URL: https://issues.apache.org/jira/browse/GEODE-2996 Project: Geode Issue Type: Sub-task Components

[jira] [Created] (GEODE-2997) New flow: putAll/getAll

Brian Baynes created GEODE-2997: --- Summary: New flow: putAll/getAll Key: GEODE-2997 URL: https://issues.apache.org/jira/browse/GEODE-2997 Project: Geode Issue Type: Sub-task

[jira] [Created] (GEODE-2998) New flow: remove/removeAll

Brian Baynes created GEODE-2998: --- Summary: New flow: remove/removeAll Key: GEODE-2998 URL: https://issues.apache.org/jira/browse/GEODE-2998 Project: Geode Issue Type: Sub-task

[jira] [Updated] (GEODE-2996) New flow: put/putAll

[ https://issues.apache.org/jira/browse/GEODE-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2996: Description: Create proto message definitions and op handler for put/putAll messages. Client

[jira] [Created] (GEODE-2999) New flow: replace/put if absent

Brian Baynes created GEODE-2999: --- Summary: New flow: replace/put if absent Key: GEODE-2999 URL: https://issues.apache.org/jira/browse/GEODE-2999 Project: Geode Issue Type: Sub-task

[jira] [Updated] (GEODE-2997) New flow: get/getAll

[ https://issues.apache.org/jira/browse/GEODE-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2997: Description: Create proto message definitions and op handler for get/getAll messages. Client

[jira] [Updated] (GEODE-2996) New flow: put/get

[ https://issues.apache.org/jira/browse/GEODE-2996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2996: Description: Create proto message definitions and op handler for put/get messages. Client should

[jira] [Updated] (GEODE-2997) New flow: putAll/getAll

[ https://issues.apache.org/jira/browse/GEODE-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes updated GEODE-2997: Description: Create proto message definitions and op handler for putAll/getAll messages. Client

[jira] [Created] (GEODE-2734) Investigate/discuss message encoding

Brian Baynes created GEODE-2734: --- Summary: Investigate/discuss message encoding Key: GEODE-2734 URL: https://issues.apache.org/jira/browse/GEODE-2734 Project: Geode Issue Type: Sub-task

[jira] [Resolved] (GEODE-2584) Client can put a register object on the server

[ https://issues.apache.org/jira/browse/GEODE-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-2584. - Resolution: Done This was based on initial protocol work, which is changing with progress toward

[jira] [Created] (GEODE-2782) Test framework: Thrift

Brian Baynes created GEODE-2782: --- Summary: Test framework: Thrift Key: GEODE-2782 URL: https://issues.apache.org/jira/browse/GEODE-2782 Project: Geode Issue Type: Sub-task Components

[jira] [Created] (GEODE-2781) Test framework: gRPC

Brian Baynes created GEODE-2781: --- Summary: Test framework: gRPC Key: GEODE-2781 URL: https://issues.apache.org/jira/browse/GEODE-2781 Project: Geode Issue Type: Sub-task Components

[jira] [Created] (GEODE-2783) Test framework: Avro

Brian Baynes created GEODE-2783: --- Summary: Test framework: Avro Key: GEODE-2783 URL: https://issues.apache.org/jira/browse/GEODE-2783 Project: Geode Issue Type: Sub-task Components

[jira] [Resolved] (GEODE-2734) Investigate/discuss message encoding

[ https://issues.apache.org/jira/browse/GEODE-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-2734. - Resolution: Duplicate This story on message encoding options superseded by other stories covering

[jira] [Resolved] (GEODE-2585) Client can get an object from the server

[ https://issues.apache.org/jira/browse/GEODE-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-2585. - Resolution: Implemented Protocol changing; will be repeated. > Client can get an object from

[jira] [Resolved] (GEODE-2746) Investigate and Evaluate Existing RPC frameworks.

[ https://issues.apache.org/jira/browse/GEODE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-2746. - Resolution: Duplicate Superseded by GEODE-2781/2782/2783 > Investigate and Evaluate Existing