v0.24.0

can handle cross-origin session/cookies(authent) when in an iframe from another origin

Full Changelog: v0.23.0...v0.24.0

v0.23.0

Revert back to v0.21.2, the only addition is :

• ServerClient.info()

Full Changelog: v0.21.1...v0.23.0

v0.22.1

BAD VERSION : don't use

fix: tag.update

Full Changelog: v0.22.0...v0.22.1

v0.22.0

BAD VERSION : don't use

• ServerClient.info() -> dict : returns more info about the current process/htag instance
• refacto : no more redys ref in appserver

Full Changelog: v0.21.1...v0.22.0

v0.21.2

exactly the same as 0.21.1 ;-)

NOTE : Seems stable in gunicorn or uvicorn.
(in fact, I thought it was not stable, because I used to test into the same navigator (chrome + private chrome), and it seems that they share some tcp sockets, and generates some troubles in server side ... and so : it was not a good idea ! With 2 different navigator : no trouble at all)

v0.21.1

• better stopServer (if exceptions in killall, it finally stop redys)
• when socket disconnect : try to wait the task cancellation

NOTE : it's not better in gunicorn ... but seems fully ok with uvicorn

Full Changelog: v0.21.0...v0.21.1

v0.21.0

• fix: htagserver.IndexApp was in global scope, so its statics were shared with all apps runned thru a htagweb server
• and hopefully : the graceful shutdown whould be there (with redys 0.9.20)

IMPORTANT : this version is great .... but with websocket mode, there are troubles... will fix soon!
you can use it in http mode, with http_only=True

Full Changelog: v0.19.0...v0.21.0

v0.19.0

new:

• time_inactivity (int, default is 0) can be specified in the AppServer constructor, or be overriden in its .handle(). when the process/instance has no activities after this time : it's suicide from itself. By default : it's 0 : so the process lives as long as the server lives (default behaviour of previous htagweb versions)
• add an UT for this

fix :

• time_interaction, defaulted to 60s (and should work has expected, now)

Full Changelog: v0.18.1...v0.19.0

v0.18.1

feat:

• time_interaction (int, default is 120s (but may be bugged)) can be specified in the AppServer constructor, or be overriden in its .handle(). It's the time after which the process is destroyed if it takes more time.
• ms windows compatible ;-)

refacto :

• redesign of hrclient (which now inherit from serverclient), and embed the ws/loop for tag.update feature
• and add a UT to test time_interaction/kill_process

Full Changelog: v0.17.3...v0.18.1

v0.18.0

a great version ;-)

Now it's really stable. And auto-kill process if an interaction is greater than 1 minute.

BTW :

• the reboot, doesn't destroy/recreate the redys server (a feature ? ;-) ... so "memory" sessions can persist)

Full Changelog: v0.17.3...v0.18.0