Thanks for this Norbert. It works great with Teapot microservices that are associated with specific JQuery widget instances. I can insert the token into the widget's callback to the pot so that only that widget instance can use that particular service. The way our web app works is that it generates a JSP with all the repetitive content / look and feel, and inserts JQuery widgets to display any dynamic data. Since the data I'm working on comes from a Pharo app I configure the JQuery widget and a pot, and supply the widget to the Java EE server from Seaside to generate the full page. The widget also keeps a lease open with the Seaside server and when the user leaves the page and the widget stops requesting the lease, Pharo can recycle the pot.
Andrew Glynn On 7/22/2016 6:12 AM, pharo-users-requ...@lists.pharo.org wrote: > An Implementation of JSON Web Tokens -- Andrew Glynn 647-539-7228 (cell/text) ☃ ☃☃ ☃☃☃ ☃☃ ☃ Burnin down the house ...
