You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by StyleTang <gi...@git.apache.org> on 2017/05/07 09:27:00 UTC

[GitHub] incubator-rocketmq-externals pull request #19: [DISCUSS]Go-Client:Detail Des...

GitHub user StyleTang opened a pull request:

    https://github.com/apache/incubator-rocketmq-externals/pull/19

    [DISCUSS]Go-Client:Detail Design

    see https://github.com/StyleTang/incubator-rocketmq-externals/tree/detail-design-rebase/rocketmq-go
    Please don't merge the PR.
    We should discuss on it.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/StyleTang/incubator-rocketmq-externals detail-design-rebase

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-rocketmq-externals/pull/19.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #19
    
----
commit 9f49aecdf1ff5da8d8e58a83c5d2c0e7b6291e1a
Author: tangjie <st...@gmail.com>
Date:   2017-05-03T15:30:34Z

    commit some remoting code which go-client will use

commit 1ce9ee0be9d346dd005b7530c318469898b7fd87
Author: tangjie <st...@gmail.com>
Date:   2017-05-03T15:39:19Z

    update remoting's roadmap

commit c528acf7b6b883fd6ce45abef77bf0e4272c78e8
Author: tangjie <st...@gmail.com>
Date:   2017-05-05T14:31:41Z

    update roadmap

commit db57f26a2bc45bc35452c46bc51338ad67d53a8b
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T06:29:55Z

    delete bak code

commit 1d2022d0150250c29cbef02cbdbeaef6e9c31533
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T08:18:13Z

    how it works and pull message timing diagram

commit 994cddede8ae3845f211ebdad597ec28ebe1468d
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T08:25:28Z

    update pull-message-timing-diagram

commit b2611ae53726aa78855f07adfbe13adfc3c0df46
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T09:20:34Z

    update rebalance-timing-diagram

commit 9e9c2302e2c953b910e0e336ec7b0d9351b7cc1c
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T09:35:38Z

    heartbeat-timing-diagram

commit 47b8dd0807ea5a60eb368f9d3e9892017a3e286b
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T09:50:41Z

    update update-topic-routeInfo-timing-diagram

commit 8b3919e268db3a91e8bc50c4daa0266e0764b9e7
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T10:01:16Z

    Millstone1 Detail Design

commit 805f0e54d94d7967c64891fca231dc88d85e45f4
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T13:05:31Z

    pull message call back

commit e6b0de3f8a2784fbb229a3927fd80010e508cacd
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T14:15:27Z

    add a consumer example

commit 01d3a383485501966415949ae271d8f4dc39d3c9
Author: tangjie <st...@gmail.com>
Date:   2017-05-06T15:10:39Z

    update rocketmq go client design

commit 6fe9dfed5c942d4bb40c342e419b7083b8be4b16
Author: tangjie <st...@gmail.com>
Date:   2017-05-07T09:20:49Z

    add ClientRequestProcessor

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-rocketmq-externals issue #19: [DISCUSS]Go-Client:Detail Design

Posted by StyleTang <gi...@git.apache.org>.
Github user StyleTang commented on the issue:

    https://github.com/apache/incubator-rocketmq-externals/pull/19
  
    As @wenfengwang 's suggestion.
    I will split MqClient into (MqClient/MqClientAPI/PullAPIWrapper)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-rocketmq-externals issue #19: [DISCUSS]Go-Client:Detail Design

Posted by StyleTang <gi...@git.apache.org>.
Github user StyleTang commented on the issue:

    https://github.com/apache/incubator-rocketmq-externals/pull/19
  
    We develop the go rocketmq client base on this design ,and the development work has been completed.
    Now we are refactoring it to make it better.
    For example, make api stable and easy to use, add test case and documents.
    see https://github.com/StyleTang/incubator-rocketmq-externals/tree/go-client-refactor
    I will send another pull request in the near future.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-rocketmq-externals pull request #19: [DISCUSS]Go-Client:Detail Des...

Posted by StyleTang <gi...@git.apache.org>.
Github user StyleTang closed the pull request at:

    https://github.com/apache/incubator-rocketmq-externals/pull/19


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-rocketmq-externals issue #19: [DISCUSS]Go-Client:Detail Design

Posted by vongosling <gi...@git.apache.org>.
Github user vongosling commented on the issue:

    https://github.com/apache/incubator-rocketmq-externals/pull/19
  
     How are things going, now :-)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---