Sorry pl. explain the "intermediary" part. Is that supposed to solve the single telnet server accepting multiple *concurrent* client sessions?
The interactive session part: not a requirement but we have no way to disallow an interactive user from telnetting when we programmatically plan to use the same IP:port. Vineet On Tue, Dec 14, 2010 at 12:28 PM, Peter Stuge <pe...@stuge.se> wrote: > Vineet Kumar wrote: >> You mean closing the telnet session after every use so that whoever >> the next guy is gets served? > > No I mean creating an intermediary that will know about your use case > and provide an interface that works. > > >> say, an interactive telnet session > > Are they a requirement in your use case? > > > //Peter > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel >
