Скачать презентацию FOS Fusebox Open Source Standards GOOD Скачать презентацию FOS Fusebox Open Source Standards GOOD

27f2e1d9afe45861e25620600fbc6367.ppt

  • Количество слайдов: 57

FOS Fusebox Open Source FOS Fusebox Open Source

Standards GOOD • Built to match needs of an environment • Proven Solutions BAD Standards GOOD • Built to match needs of an environment • Proven Solutions BAD • Environments change • Solutions change

Standards Q: What do you do if standards don’t solve the problem? A: Adaptable Standards Q: What do you do if standards don’t solve the problem? A: Adaptable Standards!

Standards Standards

Standards Strategies for change… Evolve “Naturally”: • Random changes • Things will change by Standards Strategies for change… Evolve “Naturally”: • Random changes • Things will change by natural processes • The best solution will naturally rise to the top Create • Change based on intelligence • Not being all knowing, this will not always work… but consider the alternative. • No Choice is Evolution

Standards Creative Approach Standards Creative Approach

Standards Creative Approach Benefits • Adapts to change Challenges • Change based on intelligence Standards Creative Approach Benefits • Adapts to change Challenges • Change based on intelligence • Not being all knowing, this will not always work… but consider the alternative. • No Choice is Evolution

Standards Levels of Standards Standards Levels of Standards

Standards Levels of Standards End Products Modules General Methods Development Tools Standards Levels of Standards End Products Modules General Methods Development Tools

Standards Levels of Standards ( Development Tools ) • • Hardware OS Web Server Standards Levels of Standards ( Development Tools ) • • Hardware OS Web Server SQL

Standards Levels of Standards ( Development Tools ) • • Hardware OS Web Server Standards Levels of Standards ( Development Tools ) • • Hardware OS Web Server SQL • • Intel / AMD / Ect. Windows / Linux / Etc. Cold. Fusion / on JSP MS / Oracle / Access

Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL

Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL

Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL Standards Levels of Standards ( Methodology ) • • Hardware OS Web Server SQL • • • Portability Reuse Adaptable Integration Build / Debug / Support Tiered (Data / Logic / Display) • Scales

Standards Levels of Standards ( Modules ) • • • Portability Reuse Adaptable Integration Standards Levels of Standards ( Modules ) • • • Portability Reuse Adaptable Integration Build / Debug / Support Tiered (Data / Logic / Display) • Scales

Standards Levels of Standards ( Modules ) • • • Portability Reuse Adaptable Integration Standards Levels of Standards ( Modules ) • • • Portability Reuse Adaptable Integration Build / Debug / Support Tiered (Data / Logic / Display) • Scales

Standards Levels of Standards ( Modules ) • Object Thinking – Components (user, cart, Standards Levels of Standards ( Modules ) • Object Thinking – Components (user, cart, etc. ) – Applications – Skins • • • Portability Reuse Adaptable Integration Build / Debug / Support Tiered (Data / Logic / Display) • Scales

Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, cart, etc. ) – Applications – Skins

Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, cart, etc. ) – Applications – Skins

Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, Standards Levels of Standards ( End Products ) • Object Thinking – Components (user, cart, etc. ) – Applications – Skins Pick Applications, and skins… Adapt to environment Deploy Update Friendly Borrow / Buy Others Solutions and Integrate!

Standards Standards

Standards • ABC’s Of Open Source Standards • ABC’s Of Open Source

Standards • ABC’s Of Open Source – Ants – Bees – Conies Standards • ABC’s Of Open Source – Ants – Bees – Conies

Standards • ABC’s Of Open Source – Ants • No King – (success based Standards • ABC’s Of Open Source – Ants • No King – (success based on contribution, not control)

Standards • ABC’s Of Open Source – Ants – Bees • Adapt to season Standards • ABC’s Of Open Source – Ants – Bees • Adapt to season • Prepares for changing environment • Knows when to split hive

Standards • ABC’s Of Open Source – Ants – Bees – Conies • Rock Standards • ABC’s Of Open Source – Ants – Bees – Conies • Rock Dwellers • Knows not to challenge greater foes • Knows where to take refuge

Standards • ABC’s Of Open Source Standards • ABC’s Of Open Source

Standards • ABC’s Of Open Source (These are proven survive and thrive methods. ) Standards • ABC’s Of Open Source (These are proven survive and thrive methods. ) – Know your foes, don’t challenge them. – Build on the work of others. – Change will come, contribute to it! – WE can do more than ME!

FOS • What can it do for me? – 1. 2. 3. 4. 5. FOS • What can it do for me? – 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. When you plan a web site… feature list. User Registration / Management Look and Feel Creation / Modification Administration (Users / Applications / Etc. ) Interaction / Integration Reuse existing work / amount of adaptation required Tiered Architecture RAD Tools Third Party Solutions Time To Market (Conception to Completion) Compatibility / Flexibility

FOS • What can it do for me? 1. 2. 3. 4. Better Foundation FOS • What can it do for me? 1. 2. 3. 4. Better Foundation Modular Pre-built Solutions Customize (Open Source)

FOS – Structure (Integration) FOS – Structure (Integration)

FOS – Structure (Integration) Configuration Core Objects Circuit Applications FOS – Structure (Integration) Configuration Core Objects Circuit Applications

FOS – Core Objects FOS – Core Objects

FOS – Core Objects • FOS • CORE (dynamic name through config. ) FOS FOS – Core Objects • FOS • CORE (dynamic name through config. ) FOS Core

FOS – Configuration FOS – Configuration

FOS – Configuration • Site – “site_settings. cfm” • Circuits (global) – “site_settings. cfm” FOS – Configuration • Site – “site_settings. cfm” • Circuits (global) – “site_settings. cfm” Site Circuits

FOS – Circuits (Order) FOS – Circuits (Order)

FOS – Circuits (Order) • circuit_settings. cfm • circuit_switch. cfm • [layout] Settings Switch FOS – Circuits (Order) • circuit_settings. cfm • circuit_switch. cfm • [layout] Settings Switch Skin Site Root Bundle Nest Target

FOS – Nested Inline Calls FOS – Nested Inline Calls

FOS – Nested Inline Calls • circuit_settings. cfm • circuit_switch. cfm • [layout] Request FOS – Nested Inline Calls • circuit_settings. cfm • circuit_switch. cfm • [layout] Request Site Root Bundle Nest Target Action Target Site Root Bundle Nest Target (Nested) Action

FOS – API Variables FOS – API Variables

FOS – API Variables • Request API variable structure – hj (0|1 … 1 FOS – API Variables • Request API variable structure – hj (0|1 … 1 = possible hijack attempt) – block (display groups) – circuits (circuit application settings) – site (global site application settings)

FOS – API Variables (block) FOS – API Variables (block)

FOS – API Variables (block) • request – block (display groups) • • body FOS – API Variables (block) • request – block (display groups) • • body [sidebar] [breadcrumbs] [? ? ? custom ? ? ? ] These are handled in the XDS (exit display skin).

FOS – API Variables (circuits) FOS – API Variables (circuits)

FOS – API Variables (circuits) • request – circuit (name) • • • XDS FOS – API Variables (circuits) • request – circuit (name) • • • XDS – Exit Display Skin actionname – allows for different action variable bundle – Circuit Application Collection defaultaction – If none given dir – Physical Location on System DSN – Data Source Structure – – • • • name password tables (for aliasing if used) user (Name) nest – Circuit Nesting Location objects – local circuit object location parent – name of parent circuit path – web path from root (Absolute Dynamic Reference [/ = from web root]) roles – authorized roles required to access

FOS – API Variables (site) FOS – API Variables (site)

FOS – API Variables (site) • request – Site • actionname (default action variable FOS – API Variables (site) • request – Site • actionname (default action variable for site) • app – root (main circuit) – tables (for aliasing if used) • application – name (cfapplication name) – timeout (application timeout) • core (name of core object in shared objects directory)

FOS – API Variables (site) • request – Site • • • corefile (variation FOS – API Variables (site) • request – Site • • • corefile (variation used on this site, file name) DIR (site root dir) roles (authorized roles required to access) script (default script …index. cfm / index. cfc) server – name (Web Server Name) – version (Web Server Version) • session – timeout (session timeout)

FOS – API Variables (site) • request – Site • slash (physical directory slash FOS – API Variables (site) • request – Site • slash (physical directory slash for system) • standard – – name (FOS) version (4) custom ([FOS]) customversion ([4]) • url (non-secure … this url) • urlsecure (secure … this url) • webdir (root physical directory on server)

FOS – What Next? ? ? FOS – What Next? ? ?

FOS – What Next? ? ? • • • Fusebox. INFO web site Beta FOS – What Next? ? ? • • • Fusebox. INFO web site Beta Release (Feb. 12, 2003) Exception Handler Display Handlers Documentation Example Applications

FOS – What Next? ? ? • Forum • FOS Applications – Public Domain FOS – What Next? ? ? • Forum • FOS Applications – Public Domain – Shareware – Commercial (FOS – RAD Builder) • Object Library • Versions (Win/Linux, MS SQL/Oracle/Ect. )

Contact • John. Farrar@sosensible. com • For access to Fusion Open Source beta • Contact • John. [email protected] com • For access to Fusion Open Source beta • [email protected] com