Feature to Develop : Firebase Crashlytics + Messaging #21
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
teawon
approved these changes
Dec 12, 2022
There was a problem hiding this comment.
[기본 동작원리]
- 클라이언트에서 SenderID 값 파이어베이스에 전달
- 파이어베이스에서 토큰 만들어 클라이언트로 전달
- 클라이언트는 발급받은 토큰을 서버에 전송
- 서버에서 필요에 따라 토큰값을 식별자로 메세지 전달 요청
- 파이어베이스에서 전달받은 메세지를 클라이언트앱에 전송
Q. 그냥 서버에서 바로 보내면 되는거아닌가..?
-
IOS, Android, Web등의 플랫폼에 맞춰 각각 개발해야 하지만 FCM을 사용하면 플랫폼에 종속되지 않음
-
클라우드 메세징 서버를 중간에 두면 서버에 계속 접속하지 않아도 되며 네트워크 사용및 배터리개선에 효과적
참고자료 : https://donghun.dev/Firebase-Cloud-Messaging
파이어베이스 코드에 대해서는 제가 향후 스스로 공부하는게 맞는 것 같아 기본원리만 찾아봤습니다.
잘 이해했겠죠..?
혹시 첨언이나 지적사항 말씀해주실수 있으시면 감사하겠습니다..!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#19
Features