Ok, in that case disconnection is always synchronised to any command
coming from client.
I could have imagine a way to disconnect a client that is not event
client related.
I mean a way to retrieve session from user ID, and a simple method that
close corresponding session
asynchronously, even if client is idle at this time.
Anyway, your solution is very sufficient for my needs,
thanks
On Wed, Apr 6, 2011 at 6:49 PM, frank buloup<[email protected]> wrote:
Yes ok, but it works during a connection event, No ?
How could I do if I want to disconnect a user after its connection has been
effective ?
Ftplets allow you to do this on connection events as well as before
and after commands. Is that sufficient? If not, what would trigger the
disconnect?
/niklas
--
Frank Buloup
04 91 17 22 71
Institut des Sciences du Mouvement
UMR 6233 CNRS & Université de le Méditerranée
163 avenue de Luminy
13288 Marseille Cedex 9
Fax : 04 91 17 22 52
