Ability to set local hostname sent to remote machine per session (Old Tracker 2088979)

[npeelman]

Ok, I finally figured out the use case for this, and it does present some interesting scenarios...

This guy has better explanations than i could stumble through:

http://muzso.hu/2007/11/08/cord-vs.-temporary-client-licenses
http://muzso.hu/2008/06/28/cord-v0.5.0-beta-with-client-hostname-support

Essentially when you connect to a TS Server with CoRD it uses your hostname to generate a temporary CAL. When I read these reports I was assuming they were wanting to set the hostname of the REMOTE machine in the inspector or something. But the feature request is actually the ability to set the hostname CoRD hands down to the remote machine. I'm not sure how best to handle this in the GUI without making it confusing. A "Do Not Use Default Hostname" checkbox that you can uncheck to enable a text box (That maybe gets some hostname+RandomGibberish to populate it?) is the only thing i can think of…

[arcadiclife]

We could put this on the Advanced pane.

[npeelman]

I think it should be a per-session thing though and not a global. Its only really useful for people with TS connections, i guess it really *shouldn't* matter if we were to send hostname+random to all hosts when its turned on, but I could see that having other implications. I think restricting the scope to per-session would be our best bet.

[arcadiclife]

Maybe we should change the inspector to use a tab-based layout (similar to the prefpane)? that would allow us to put more stuff in it

[npeelman]

I was hoping you'd suggest that :) I was thinking it but didn't want to bring it up. I really don't want to use a TabView?'s ugly tabs though. I liked my SegementedCell? bound to a Tabless TabView?.

http://peelman.us/files/images/cord-inspector-1.png
http://peelman.us/files/images/cord-inspector-2.png

Doesn't have to be that specifically, but something other than the standard fugly tabviews would be great :)

[arcadiclife]

Marked #94 as a dupe of this.

[muzso]

Replying to arcadiclife:

Marked #94 as a dupe of this.

Sorry for not having spotted this ticket. I really _did_ scan through the open ticket titles before I created #94, but I looked only at "functionality enhancements" and not defects. I've changed the ticket to "functionality enhancement" since this is definitely not a defect.

As for your question ...

Do you think this feature is OK to be set on a global basis, or does it need to be set separately for each saved server?

Imho it should be a per-server setting and not global. It's only useful if you're using the server with normal users. The Windows server won't require a temporary license for members of the Administrators group (at least with Win2003 ... I'm not familiar with Terminal Services in Win2008).

I've attached a screenshot of my patched CoRD where you can take a look at my choice for the placement of the client hostname input field. Of course this is nothing fancy ... I've never before worked with Xcode or any Mac projects. :-)

[arcadiclife]

if/when we implement this, it won't be inline with the other options. Only ~5% of CoRD users will care about this, so I don't want the 95% to see it. thanks for the input--we'll do this as a per-server, instead of global setting

we have a number of other niche options we want to implement, so we'll probably be moving to a tab-based inspector

[muzso]

Replying to arcadiclife:

if/when we implement this, it won't be inline with the other options. Only ~5% of CoRD users will care about this, so I don't want the 95% to see it.

Ok, you're absolutely right. Thanks for considering this feature for implementing in CoRD. :-)

[npeelman]

This has been partially implemented in r564. You can now set the sent hostname globally for all sessions. Once we redesign the inspector we’ll work in the ability to set it per-session.

[npeelman]

Ok, for now I’m moving this to 0.7. Hopefully by then we’ll have the inspector redesigned and be able to add this in as a per-session option.