Bug 142969 - [api] For "Running" dstore launcher, the "port" Property should be with Connectorservice (and not with subsystem)
Summary: [api] For "Running" dstore launcher, the "port" Property should be with Conne...
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: Future   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on:
Blocks: 158726 160020
  Show dependency tree
 
Reported: 2006-05-22 07:52 EDT by Martin Oberhuber CLA
Modified: 2010-03-12 21:04 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2006-05-22 07:52:31 EDT
The "port" property for the "Running" server Launcher should be ediatble in the New Connection Wizard, under Launcher Properties.

Currently it is only editable in the Subsytem Properties, which means it must be changed for each subsystem separately.
Comment 1 David McKnight CLA 2006-05-23 13:48:23 EDT
This is probably something that needs to be addressed more broadly. For other server launchers, like the daemon, there are two ports involved.  First, there is the port used to connect to the daemon, and then there is the port to use when connected to the dstore server (which is different).  The port specified in the subsystem properties is this port, in either case (daemon or running server).  This separation has been a confusion for a lot of users in the past so I agree we ought to move all ports to one place.  I think we ought to do away with the subsystem port property altogether in favour of something more tied to the connector service.  Any other opinions?
Comment 2 David Dykstal CLA 2006-05-23 14:12:26 EDT
There are probably several things other than ports that need to be tied to the connector service rather than the subsystem. If we did this we could probably get rid of the whole notion of a "primary" subsystem. So here's the list so far:
daemon port
session port
default default user id (this is a guess, probably not needed)

However, it probably makes more sense to make these items in a "connection" property set rather than part of the common description of a connector service since there are connector services that will need completely different descriptions - eg serial port settings.
Comment 3 Martin Oberhuber CLA 2006-07-03 08:39:10 EDT
Marking as [api] since this changes they way how connection properties are handled, and probably also the notion of whether a "primary subsystem" exists or not.
Comment 4 David McKnight CLA 2006-09-18 11:24:44 EDT
Not going to be handling this at moment, so I'm lowering the priority.
Comment 5 Martin Oberhuber CLA 2007-05-18 16:04:29 EDT
Not for 2.0