URL bar, wildcard/global profiles
By packetb... on May 10, 2011 19:12 (imported from Google Code)
Instead of profiles associated with a single host, this would let you define a profile for any connection based on subnet, domain protocol, command or hostname. For example, in organizations with lots of Cisco devices, it would be tedious to create a new profile for each device.
This could be enhanced with Chrome-style keywords. For instance, if the first word in the address bar is not a url qualifier, it is interpreted as the name of a global profile, and if no match exists as a command. That way, you can type 'switch ssh://10.1.0.52' and the global profile named 'switch' would be applied, or 'login -fp user' for a local shell.
An example of a profile wildcard could be: 'telnet://.apple.com' for any telnet sessions to devices in the apple.com domain, or '192.168.1.0/24' for any devices in this subnet, regardless of protocol, or 'ssh://' for any secure shell sessions.