Differences

This shows you the differences between the selected revisions of the page.

2013-12-20 2013-12-20
5.5 no pages on login dialog (martin) not recommending to use sites for scripting (martin)
Line 4: Line 4:
When configuring a session, most often you set a //Protocol//, //Host name// and //User name//. When configuring a session, most often you set a //Protocol//, //Host name// and //User name//.
-Session is usually configured on a [[ui_login|Login dialog]].·In [[scripting]] and on [[commandline|command-line]] session is configured using [[session_url|session URL]] and some additional switches.+Session is usually configured on a [[ui_login|Login dialog]]. 
 + 
 +In [[scripting]] session is configured using [[session_url|session URL]] and some additional switches of ''[[scriptcommand_open|open]]'' command. On [[commandline|command-line]] you can also use session URL and some additional switches.
===== [[site]] Sites (Stored Sessions) ===== ===== [[site]] Sites (Stored Sessions) =====
Line 10: Line 12:
To store session configuration use //Save button// on the [[ui_login|Login dialog]]. The [[ui_login_save|Save session as Site]] dialog will appear. To store session configuration use //Save button// on the [[ui_login|Login dialog]]. The [[ui_login_save|Save session as Site]] dialog will appear.
- 
-You will find Sites useful also for [[scripting]] to configure session options that cannot be configured using scripting commands directly. 
Note that even when you have already logged in, you can still [[task_connections#saving_opened_session|store the opened session]]. Note that even when you have already logged in, you can still [[task_connections#saving_opened_session|store the opened session]].

Last modified: by martin