|
|
|
|
|
by bob1029
730 days ago
|
|
My most recent workaround for this is to put a session identifier in the URL somewhere and keep literally everything else on the server. You essentially have to build your app from zero with these limitations in mind if you want any chance at getting around them. This is a large part of why I am not a fan of frameworks and other popular design patterns. Having total control over how state is managed and communicated is really important if you don't want to get trapped in various tar pits. |
|