Difference between revisions of "User:Exor674/Journalspace Path"

Revision as of 00:44, 1 February 2012

Apache::LiveJournnal::trans

$determine_view inline sub in ::trans

• Check for a Routing call in the user role

If one exists, we do that and are done

• Failing that..

There are some special cases here ( __setdomsess, redirect journals ), but otherwise this determines the view and prepares to call top the next step.

$journal_view inline sub in ::trans

• Check if we should show the adult content interstial ( if so show it and we are done! )

• /info is a redirect to full profile ( we're done )

• profile is ( currently ) a call into BML ( we're done )

• update is a redirect to the update page ( we're done ) NTS: move this to a routing call!

• Data handlers ( we're done )

Customview is diffrent!!!

customview

otherwise (Apache::LiveJournal::journal_content)

This is one of the main meats of the operation!

• Handle robots.txt ( we're done )

• Handle auth=digest ( we're done unless the user is already authenticated )

• handle failed cookies, or stuff. ( we're done if cookies have failed )

• Set up to call into make_journal

LJ::make_journal

back in (Apache::LiveJournal::journal_content)

• Add extra hooks if we didn't go down the siteviews path.

• If make_journal requested an internal_redirect [internal_redir], call into routing with it. ( we're done )

• If make_journal requested a redirect [redir], well, redirect ( we're done )

• If make_journal requested a direct return [handler_return], return that ( we're done )

• If we went down the siteviews path, render that result in sitescheme ( we're done )

• If a BML handler was requested, determine which bml file we need to render and render it. ( we're done )

• .. bleh a lot more stuff ( 1412 to 1521, don't want to summarize now QQ )