Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Issues with idom.run and SharedClientStateServer #711

rmorshea started this conversation in General
Discussion options

@jmtaysom was having some issues with idom.run when using Sanic as well as with Sanic's SharedClientStateServer (previously discussed here).

You must be logged in to vote

Replies: 2 comments 3 replies

Comment options

rmorshea
Mar 17, 2022
Maintainer Author

@jmtaysom what version of Sanic are you using?

You must be logged in to vote
2 replies
Comment options

Sanic 21.12.1

Comment options

rmorshea Mar 17, 2022
Maintainer Author

IDOM presently requires sanic>19,<19.12 - see here for more info. The other async server implementations should work fine without this limited range of versions.

Again, apologies for all these limitations. I'm presently working on a PR which will address most of the problems we've talked about:

  • Rework idom.run
  • Remove SharedClientStateServer
  • Fix limited support for sanic
  • etc.
Comment options

rmorshea
Mar 17, 2022
Maintainer Author

Also, apologies for the sweeping changes here, but SharedClientStateServer is slated for removal since it doesn't work with multi-process web servers. Instead we would need to provide a more robust solution that would work across processes and hosts - probably using something like Redis.

You must be logged in to vote
1 reply
Comment options

That makes a lot of sense. If it is slated for removal I would remove it from the beginning of the tutorial just to not confuse people.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /