Opened 11 years ago
Closed 11 years ago
#2903 closed enhancement (wontfix)
Enhancement of the source directory structure
Reported by: | avs1978 | Owned by: | |
---|---|---|---|
Priority: | trivial | Component: | General |
Severity: | medium | Keywords: | Directory structure |
Cc: | Sensitive: | no |
Description
Reason for enhancement
Increase find-ability and program structure. Promote, quasi object oriented programming.
Possible impacts on other features
During initial phase of this project, none, because files are only moved to different directories. Later on, who knows?
Attachments (3)
Change History (7)
comment:1 by , 11 years ago
Severity: | low → medium |
---|
comment:2 by , 11 years ago
Look, this is silly idea. Just drop it. The oscam source code is already separated logically (there are small things left here and there, where they don't belong, but I'm fixing this slowly).
Moving one source file per directory would bring us nothing but pain for the poor svn users that miss "git grep" and tools like that.
by , 11 years ago
Attachment: | directory_tree_simplified.txt added |
---|
comment:4 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
General idea is the create clear interfaces between the different building blocks (modules).
If I interpreted the wiki and docs correctly, then OSCam is more than a softcam or cw/ecm router. The core of OSCam is its CW/ECM router proxy functionality, the card share proxy router (CSP).
A simple example of clear interfacing and how to enhance it.
Lets take a simple STB with hardware CAM-module and smartcard. We are watching an encrypted channel. What is happening: the stream processor discovers it needs to decrypt video and/or audio. It provides the ECMs (video and/or audio) over common interface (CI) bus to the CAM-module. CAM-module, selects correct ECMs and request CW from smartcard.
OSCam could do something similar. DVBapi discovers it needs a CW and request for it through its client module, based on CI methodology. The client module request CW from CSP. The receives to types of information client login and functionality rights (groups, services, etc.) together with the ECM to CW requests packaged according to CI methodology.
The CSP of course does some nifty loadbalancing and rerouting to select the correct server. The selected server gets the ECM to CW request based on the CI methodology.
Please some comments, also about the directory tree.