Okay. Thank you very much for the info.
On Mon, May 1, 2017 at 1:42 PM, Chris Poulsen
wrote:
> Your means to securing a "traditional tapestry page" (filter based
> approach) should be sufficient.
>
> On Mon, May 1, 2017 at 6:39 AM, abangkis wrote:
>
> > Hi, with the client-side API release in T
Hi,
Thanks for the answer. I will look into that.
Best regards,
Miguel
On Sun, Apr 30, 2017 at 10:12 PM, Lance Java
wrote:
> tapestry-cometd uses tapestry-offline under the hood to fool tapestry into
> believing it was invoked via a request / response when it was actually
> invoked via websock
