Bug 231101 - [api] Remote File should have a bidiOptions member to hold its bidi attributes
Summary: [api] Remote File should have a bidiOptions member to hold its bidi attributes
Status: NEW
Alias: None
Product: Target Management
Classification: Tools
Component: RSE (show other bugs)
Version: 2.0.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: dsdp.tm.rse-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords: api
Depends on: 244041
Blocks:
  Show dependency tree
 
Reported: 2008-05-08 07:35 EDT by Ramy Said CLA
Modified: 2008-08-14 07:30 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ramy Said CLA 2008-05-08 07:35:52 EDT 
A bidiOptions member is needed for the RemoteFile type to hold its bidi attributes. A setter/getter of this bidiOptions object are needed to be able to set/get the bidiOptions value for some remote file.
Comment 1 Martin Oberhuber CLA 2008-05-08 15:05:24 EDT 
We are past API freeze. Please think about ways for adding your settings to the IRemoteFile by means of your own adapter factory or similar.

If I'm not mistaken we've had a somewhat related request before. Please search bugzilla, the comments on that bug include some ideas for how to integrate BIDI support without changing RSE API. I believe that Violaine Battish was on that other bug.

If you are not asking for API here but something else, please let me know. I'm assigning this request to future for now.