https://github.com/zinaaan/im-system

Instant Messaging system implemented by Netty and Spring-boot
https://github.com/zinaaan/im-system

instant-messaging java java-8 mybatis-plus netty redis redisson spring-boot tcp-server websocket

Last synced: 2 days ago
JSON representation

Instant Messaging system implemented by Netty and Spring-boot

• Host: GitHub
• URL: https://github.com/zinaaan/im-system
• Owner: Zinaaan
• Created: 2023-05-31T02:22:49.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-10-22T22:15:24.000Z (about 1 year ago)
• Last Synced: 2024-10-11T08:41:38.097Z (25 days ago)
• Topics: instant-messaging, java, java-8, mybatis-plus, netty, redis, redisson, spring-boot, tcp-server, websocket
• Language: Java
• Homepage:
• Size: 221 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
im-system

===========================

Instant Messaging system implemented by Netty and Spring-boot

## Catalog

* ### im-system

    * [im-codec](#im-codec)

    * [im-common](#im-common)

    * [im-message-store](#im-message-store)

    * [im-service](#im-service)

    * [im-tcp-gateway](#im-tcp-gateway)

### [im-codec](./im-codec)

Customize transmission protocol for Instant Messaging system

***

### [im-common](./im-common)

***

### [im-message-store](./im-message-store)

***

### [im-service](./im-service)

***

### [im-tcp-gateway](./im-tcp-gateway)

***

### Useful commands

Redis startup in windows(locate to the redis directory):

`redis-server.exe redis.windows.conf`

## Process of checking friendship

The request data: 

`{

     "appId" : 10000,

     "fromId" : "lld",

     "toIds" : ["lld2", "lld4", "lld5", "8888888"],

     "checkType" : 2

 }`

 

 **fromId:** the id for a current user 

 

 **toIds**: the friend id array of current user

 

 **checkType**: '1' means one-way verification, whereas '2' means two-way verification

 

#### Check friendship status (determined by requesting side)

**One-way verification**

1. '1' means that only checking if current user (fromId) has added the corresponding friend (toId)

2. '0' means that only checking if current user (fromId) didn't add the corresponding friend (toId)

**Two-way verification**

1. '1' means that two people (fromId and toId) are already friends

2. '2' means that current user (fromId) has added the corresponding friend (toId), but the corresponding friend didn't add the current user as a friend

3. '3' means that current user (fromId) didn't add the corresponding friend (toId), but this friend has added the current user as a friend

4. '4' means that two people (fromId and toId) are not friends

## Process of checking blacklist relationship

The request data: 

`{

     "appId" : 10000,

     "fromId" : "lld",

     "toIds" : ["lld2", "lld4", "lld5", "8888888"],

     "checkType" : 2

 }`

 

 **fromId:** the id for a current user 

 

 **toIds**: the friend id array of current user

 

 **checkType**: '1' means one-way verification, whereas '2' means two-way verification

 

#### Check blacklist status (determined by requesting side)

**One-way verification**

1. '1' means that only checking if current user (fromId) has blacked out the corresponding friend (toId)

2. '0' means that only checking if current user (fromId) didn't black out the corresponding friend (toId)

**Two-way verification**

1. '1' means that two people (fromId and toId) are not blacked out with each other

2. '2' means that current user (fromId) has blacked out corresponding friend (toId), but the corresponding friend didn't black out current user as a friend

3. '3' means that current user (fromId) didn't black out the corresponding friend (toId), but this friend has blacked out the current user as a friend

4. '4' means that two people (fromId and toId) are both blacked out with each other