Le 26 novembre 2018 14:35:10 GMT+01:00, "André Warnier (tomcat)"
a écrit :
>On 26.11.2018 13:29, Rémy Maucherat wrote:
>> On Sat, Nov 24, 2018 at 9:48 AM Ludovic Pénet
>wrote:
>>
>>> Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
Le vendredi 23 novembre 2018 à 23:51 +0100, Rémy Maucherat a écrit :
> On Wed, Nov 21, 2018 at 10:58 AM Mark Thomas
> wrote:
>
> > - French has increased from 18% to 64% coverage
> >
>
> Done (well, close enough, a few tribes/ha remain) !
A single translation remains to be performed.
Jump to
Le mardi 13 novembre 2018 à 16:39 +0100, André Warnier (tomcat) a
écrit :
> On 13.11.2018 13:32, Rémy Maucherat wrote:
> > On Mon, Nov 12, 2018 at 12:49 PM Mark Thomas
> > wrote:
> >
> > > I'm aiming to export the translations on a regular basis to the
> > > Tomcat
> > > source code. How
In a similar situation, I do the following :
* go full stateless, use no session ;
* configure WS client to frequently reconnect
* use atmosphere with an internal JMS backend, such as ActiveMQ, to share data
transparently between parallely deployed versions.
With Atmosphere, you avoid losing
On 10/03/2017 02:41, radiatejava wrote:
Tomcat team, I have few questions on websocket:
Hi.
I am not member of the Tomcat team, but I will try to give you some
answer or hints...
[...]
2. Is there any sample code for how to put in SSL (keystore and
truststore) websocket client ?
You
Hi.
As kindly advised, I restart this question as a separate thread.
Is there a standard, easy way to reread roles for an authenticated user ?
The use case is as follow : I implement JSON web tokens (JWT) as a valve,
generating it after the container performed authentication and restoring
Hi.
I have a question relating to your thread (at least in my mind) : is there a
standard, easy way to reread roles for an authenticated user ?
The use case is as follow : I implement JSON web tokens (JWT) as a valve,
generating it after the container performed authentication and restoring
SOAP and REST are of different natures. SOAP is more of a protocol. REST is an
architectural style.
You will find a more elaborate explanation on this stackoverflow thread
http://stackoverflow.com/questions/19884295/soap-vs-rest-differences
For the rest part, I use both RESTEasy
Not always predictable (you expect no more than 99 versions and finally have).
Can be against conventions.
Le 2 octobre 2015 13:07:15 GMT+02:00, David kerber a
écrit :
>On 10/2/2015 4:33 AM, l.pe...@senat.fr wrote:
>> Hi.
>>
>> I am using parallel deployment to upgrade
>> You have competing requirements:
>>
>> 1. All servers are the same
>>
>2. Some subset users get a different version of the application
>>
>
>All servers would have all versions of the app, thats the whole point
>:)
>I.e.
>Instead of
>Server 1 - 3: App Version 001
>Server 4 - 6: App Version
I can't see what would be the risks with being able to explain "This account is
locked for X minutes"...
I experienced situations where the user calls the first level service desk and
a ticket goes all its way to someone who can read the server logs and
understand the issue... Not exactly
16:54:20 GMT+02:00, Christopher Schultz
<ch...@christopherschultz.net> a écrit :
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Mark,
>
>On 8/31/15 6:42 AM, Mark Thomas wrote:
>> On 31/08/2015 07:32, Ludovic Pénet wrote:
>>> I can't see what would
12 matches
Mail list logo