Your SlideShare is downloading. ×
0
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Introduction to ColdCourse
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Introduction to ColdCourse

890

Published on

Presentation to Adogo on ColdCourse. You can also view the recording of this presentation.

Presentation to Adogo on ColdCourse. You can also view the recording of this presentation.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
890
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SES URL’s for ColdFusion with ColdCourse Adobe Developers of Greater Orlando adogo.us September 2007
      • Search Engine Safe URLs for Fusebox, Mach-II, Model-Glue, ColdBox and more.
  • 2. What's this ColdCourse thing?
    • An addon for MVC frameworks to allow for pretty URLs
    • Executes before the framework
    • Works with any CF MVC framework if some conventions used
    • Based on ColdFusion on Wheels routing engine
  • 3. What else does it do?
    • Single config file to setup.
    • Caches found courses
    • Optional single location for all resources
    • Provides redirects (301 Moved Permanently)
  • 4. Sample Course User navigates to: http://localhost/home/about URL routing rules (.htaccess for apache, isapi filter for IIS) change this to http://localhost/index.cfm/home/about In index.cfm, before the framework is included ColdCourse evaluates this and executes the following. <cfset url['fuseaction'] = “home.about” /> because it matches a default course: <cfset addCourse(“:controller/:action”) /> Since most frameworks rely on a single variable passed through the URL, they don't care if it was set by the URL, or set to the URL scope.
  • 5. More Complex Example User navigates to: http://localhost/users/BrianLeGros The following routing rule is declared <cfset addCourse(“users/:username”, controller=”user”, action=”view”) /> ColdCourse does the following: <cfset url['fuseaction'] = “user.view” /> <cfset url['username'] = “BrianLegros” /> This would in effect be the same as http://localhost/index.cfm?fuseaction=user.view&username=BrianLegros
  • 6. Any Problems With This?
    • Every course needs a “controller” and an “action”.
    • Relative links and paths within existing applications
    • Legacy POST actions must be changed.
    • Calls from within a framework?
  • 7. How does that Work?
    • Code example
  • 8. Thanks!
      • Resources :
      • ColdFusion on Wheels - cfwheels.com
      • Ruby On Rails - rubyonrails.com
      • ColdCourse available at coldcourse.riaforge.com
      • Code available at http://svn.adogo.us

×