What does the session detaching/resuming mean?
290 A: The new SILC protocol supports a feature called session detachment. 291 This means that client can detach from the server by giving a DETACH 292 command, but still remain as valid user in the network. The connection 293 is lost to the server but the user remains in the network. User can 294 then resume the session back next time it connects a server in the 295 network, and be like he was never gone. 296 297 This feature clearly could be used in many cases. For example, if you 298 want to upgrade your current SILC client, you do not have to quit the 299 network anymore. You just give DETACH command and still remain in the 300 network. Then you upgrade your client and reconnect to the server and 301 continue business as is. If somebody gives WHOIS command to your 302 nickname he will see that you are detached. Messages that are sent to 303 you when you are detached are dropped by the server. Nice thing about 304 this feature is also that you can resume the session from any server
The new SILC protocol supports a feature called session detachment. This means that a client can detach from the server by giving a DETACH command, but still remains as a valid user in the network. The connection is lost to the server but the user remains in the network. User can then resume the session back next time it connects a server in the network, and be like he was never gone. This feature clearly could be used in many cases. For example, if you want to upgrade your current SILC client, you do not have to quit the network anymore. You just give DETACH command and still remain in the network. Then you upgrade your client and reconnect to the server and continue business as is. If somebody gives WHOIS command to your nickname he will see that you are detached. Messages that are sent to you when you are detached are dropped by the server. Nice thing about this feature is also that you can resume the session from any server in the network; you do not have to reconnect to the same s
