xuhe2 opened a new issue, #916:
URL: https://github.com/apache/dubbo-go-samples/issues/916

   Currently, the `dubbo-go-samples/registry` directory only contains examples 
for Nacos and ZooKeeper, but lacks an example for etcd. 
   > I noticed that the previous commit included an etcd implementation.
   
   I've written sample code for the etcd registry, located in 
dubbo-go-samples/registry/etcd.
   > I referenced the ZK and Nacos documentation.
   
   **I've finished writing the code and tested it locally. I'd like to submit a 
pull request to contribute this example. Is this PR acceptable to the 
community?**
   
   ```
   .
   ├── etcd
   │   ├── go-client
   │   │   └── client.go
   │   ├── go-server
   │   │   └── server.go
   │   └── proto
   │       ├── greet.pb.go
   │       ├── greet.proto
   │       └── greet.triple.go
   ├── nacos
   │   ├── go-client
   │   │   └── cmd
   │   │       └── client.go
   │   ├── go-server
   │   │   └── cmd
   │   │       └── server.go
   │   ├── proto
   │   │   ├── greet.pb.go
   │   │   ├── greet.proto
   │   │   └── greet.triple.go
   │   └── README.md
   ├── README.md
   └── zookeeper
       ├── go-client
       │   └── cmd
       │       └── client.go
       ├── go-server
       │   └── cmd
       │       └── server.go
       ├── proto
       │   ├── greet.pb.go
       │   ├── greet.proto
       │   └── greet.triple.go
       └── README.md
   
   17 directories, 18 files
   ```
   
   <img width="1898" height="950" alt="Image" 
src="https://github.com/user-attachments/assets/9d6a7b07-b766-4b68-a0a2-2bd2f9ae6c97";
 />
   
   > it works


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to