|
-
Feb 18th, 2014, 10:51 AM
#1
Thread Starter
Frenzied Member
Advice on naming (Account vs Connection)
So I'm working on building an application that at it's core will provide connections to various server types (FTP, WWW, etc). The application will allow the user to store these connections for later use via a "Connection Manager." I'm struggling with what to actually name these "items" being saved. The verb is "Connect" and ultimately I am calling it a "Connection" when the user has actually established a live connection to the server, but when in this "Connection Manager" screen, should I call them "Accounts?" The reason I ask is that to me, an "Account" would be the non-instantiated word for "Connection", since it's not a "connection" until it has been actually established. But then again, if I call it "Account Manager" that seems to imply the management of the actual accounts on the servers, which it is not.
This question is geared towards not only what the end user will see, but what I should be calling the .NET objects I'm using to represent these in code. AccountObject or ConnectionObject??
I have seen different applications call these different things like "sessions", "accounts", "connections", etc...
Any and all advice is welcome.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|