django channel save chat record upon last user leave the room
Hi I am new to any Async coding hence the great django-channels official lib is a bit obfuscated to me.
I was able to define a ORM process upon message send to save the message to db. That will be easy.
However, imagine 5000 users sending messages simultaneously. The db will easily be overloaded even if I use a celery task queue. Plus the db could easily accumulate millions of rows in a short period.
I imagine there to be a way to gather all lingering messages in the channel-layer, and upon layer close (last user exit, websocket connection = 0), save these into a JsonField as one row?
TLDR: how to check layer termination, and after that how to get all messages sent? Where are they stored, in memory?
Current thought on a naive method: create a memory register (like database, but in memory only) for each channel and place all messages there as they sent. Then when the websocket terminates, trigger a save code. But then, how to create this kind of fake-db that only exist in memory?
Appreciate all suggestions!
websocket chat python-asyncio django-channels chatroom
add a comment |
Hi I am new to any Async coding hence the great django-channels official lib is a bit obfuscated to me.
I was able to define a ORM process upon message send to save the message to db. That will be easy.
However, imagine 5000 users sending messages simultaneously. The db will easily be overloaded even if I use a celery task queue. Plus the db could easily accumulate millions of rows in a short period.
I imagine there to be a way to gather all lingering messages in the channel-layer, and upon layer close (last user exit, websocket connection = 0), save these into a JsonField as one row?
TLDR: how to check layer termination, and after that how to get all messages sent? Where are they stored, in memory?
Current thought on a naive method: create a memory register (like database, but in memory only) for each channel and place all messages there as they sent. Then when the websocket terminates, trigger a save code. But then, how to create this kind of fake-db that only exist in memory?
Appreciate all suggestions!
websocket chat python-asyncio django-channels chatroom
add a comment |
Hi I am new to any Async coding hence the great django-channels official lib is a bit obfuscated to me.
I was able to define a ORM process upon message send to save the message to db. That will be easy.
However, imagine 5000 users sending messages simultaneously. The db will easily be overloaded even if I use a celery task queue. Plus the db could easily accumulate millions of rows in a short period.
I imagine there to be a way to gather all lingering messages in the channel-layer, and upon layer close (last user exit, websocket connection = 0), save these into a JsonField as one row?
TLDR: how to check layer termination, and after that how to get all messages sent? Where are they stored, in memory?
Current thought on a naive method: create a memory register (like database, but in memory only) for each channel and place all messages there as they sent. Then when the websocket terminates, trigger a save code. But then, how to create this kind of fake-db that only exist in memory?
Appreciate all suggestions!
websocket chat python-asyncio django-channels chatroom
Hi I am new to any Async coding hence the great django-channels official lib is a bit obfuscated to me.
I was able to define a ORM process upon message send to save the message to db. That will be easy.
However, imagine 5000 users sending messages simultaneously. The db will easily be overloaded even if I use a celery task queue. Plus the db could easily accumulate millions of rows in a short period.
I imagine there to be a way to gather all lingering messages in the channel-layer, and upon layer close (last user exit, websocket connection = 0), save these into a JsonField as one row?
TLDR: how to check layer termination, and after that how to get all messages sent? Where are they stored, in memory?
Current thought on a naive method: create a memory register (like database, but in memory only) for each channel and place all messages there as they sent. Then when the websocket terminates, trigger a save code. But then, how to create this kind of fake-db that only exist in memory?
Appreciate all suggestions!
websocket chat python-asyncio django-channels chatroom
websocket chat python-asyncio django-channels chatroom
asked Nov 12 '18 at 14:05
Exis ZhangExis Zhang
1113
1113
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263826%2fdjango-channel-save-chat-record-upon-last-user-leave-the-room%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53263826%2fdjango-channel-save-chat-record-upon-last-user-leave-the-room%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown