1 / 27

TOC

Special-purpose application servers Gregor J. Rothfuss Technical Director PostNuke O’Reilly Open Source Convention July 22-26, 2002. TOC. Whats wrong with app servers? The product The community The architecture The uses The future Q & A. Whats wrong with app servers?.

anthea
Download Presentation

TOC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Special-purpose application serversGregor J. RothfussTechnical DirectorPostNukeO’Reilly Open Source ConventionJuly 22-26, 2002

  2. TOC • Whats wrong with app servers? • The product • The community • The architecture • The uses • The future • Q & A

  3. Whats wrong with app servers? • Supposition: Most programmers suck • App servers mainly support „good“ programmers • App servers are too generic, too high level

  4. Special purpose app servers • Tenet: Provide cool stuff out of the box • Libraries alone dont woo anyone • Provide approaches on several levels • customization (Administration) • skinning (Layout) • addon development • Examples of this breed: • Midgard, PhpGroupware, PostNuke

  5. Dedication: Greg Allan • Greg Allan a.k.a. Adam_Baum, the lead core developer and one of the four founding members of the PostNuke Development Project passed away from injuries sustained in a motorcycle accident. The accident occurred June 16, 2002 near his home in Meaford, Ontario in Canada.

  6. Product: Some stats • 500,000 downloads to date • 20,000 sites running • 120+ modules available • 100+ themes available • PostNuke is IBM Server proven

  7. Product: Target audiences • Private persons • Communities • Small businesses • Needs to • be easy to install, admin • have a good support infrastructure • run anywhere

  8. Product: Why PHP? • Runs on most ISPs • Is easy to learn • Large amounts of legacy code • Cross platform: PN runs on Linux, Windows, OS 390, Solaris • Lean & mean

  9. Product: Core Features • User management • Permissions • Templating • Modularity

  10. The PostNuke community • 200+ developers • 20 international support sites • 14,000 registered users • Bottom line: PostNuke is about building and growing communities

  11. Architecture: Goals • provide compatibility for modules • encourage code reuse • provide a secure environment • keep it as easy as possible (but no easier)

  12. Architecture: Flow pnInit pnInit Sess Lang DB Site Sess DB Module(s) XML-RPC specific API Templates Theming Web (XHTML) RPC (XML)

  13. Architecture: Components Themes / Templating Modules Blocks Utility Modules PN API ADODB DB: MySQL, Postgres, MSSQL, Sybase, Oracle

  14. Architecture: Module Design • Separation of User and Admin Functions • Separation of Display and Operational Functions • Single Directory Installation • External Access to Module Functions

  15. Architecture: Hooks • Modules can register hooks that will be called on specific events: • Item creation • Item display • Modules dont know who if anyone will implement their hook • Examples • Admin notification on user signup

  16. Architecture : Cron • Modules can schedule events to occur on a regular basis • Examples: • Notification mails • Cleanup tasks • Syndication

  17. Architecture : Permissions • ACL based on regular expressions • Supports unlimited groups • Supports nested groups • Can be a challenge to understand • Simpler admin interfaces in development

  18. Architecture : Syndication • Exchange site headlines with other sites • Based on RSS 0.91 • Format supported by hundreds of sites: • Reuters

  19. Architecture : ADODB • Based on MS ADODB API principles • Strive for SQL 92 compatibility • Remaining quirks: JOIN, Auto-increase fields • CREATE TABLE is hard..

  20. armorama.com

  21. www.fzln.org.mx

  22. Hagerstown Business College

  23. Government of Bahrain

  24. Usage Scenarios Community WebsitesForums, News, Syndication Small BusinessesShopping solutions, CMS Vertical Solutions pnCommunitypnEducation

  25. The Future • support more databases • make module writing easier • develop more vertical solutions • port PostNuke to Midgard • increased scalability • rich applications

  26. Q & A

More Related