Tim, > > */Home Page:/* > > Use a normal dmHTML page with a display method using cfmodule or > > cfinclude to include the table (will be list) of subjects. This will use > > the buildlink tag to create the links based on navalias of the courses > > (see below). > > Sounds alot like a publishing rule to me. IMO generally most things are > best implemented as either dmInclude or a publishing rule -- allows > reconfiguration without having to change any physical files and you have > less templates. If you want to share the rule amongst certain pages then > you could either make a new template, change an existing template, make > your rule aware of where its being called from and only display when > neccessary or make a second rule which modifies the content of the first > rule depending on where its being called from.
Yeah, maybe you're right. I think i should probably use a publishing rule. > > And then the url would be /go/mcq/hsc/Mathematics > > > > The navalias for each subject would be say subject_12345 where 12345 is > > the subject id. This means the my include on the home page could loop > > thru the subjects and do a buildlink based on “subject_” & subject_id. > > If the navalias was subject_12345 then the url would be not as above but as: > /go/mcq/hsc/Mathematics_12345 As far as i know, the FU is on navigation node title rather than nav alias. So the nav node title could be "Mathematics" and the navalias could be subject_12345. > > The redirect when this is completed is not done yet because CFCOOKIE may > > be used on this page, and if it is that messes up using a CFLOCATION. I > > was thinking of using getPageContext().forward(url) to send the user to > > the test page….. > > Well apart from the cookie issue this will probably will nicer for the > user anyway. I now set a request variable when cfcookie is used. if this is present i do a javascript redirect with a link displayed if the JS doesnt work, if not i just use CFLOCATION. > > Is this the right way to be going about it, or should I be using custom > > types or something else? > > I guess it depends how much of the FarCry framework you want to > leverage. If you plan on moving this app to be more FarCry centric > (which is what it sounds like as you want to use the tree etc) then > custom types and publishing rules are most flexible. > > If you want to keep the app portable and usable outside the framework > then you may want to stick with includes -- although none of your app > logic would have to change if using custom types and publishing rules so > I don't see why you'd stay with includes. Yes, i may want to keep it portable, so i may stick with includes for the spec test page and publishing rule for the home page. > > I am expecting up to a few hundred thousand page views in this part of > > the site per day around the time of the real HSC exams in October/ > > November. This is based on 20,000 tests or more by 5 or ten page views > > per test. If I have my navigation etc cached properly do you think > > farcry would be ok for this task? > > Not sure about the load (you'd have to make a proof-of-concept and test > this yourself). Its very easy to add caching around containers in > templates. You'd have to deal with your own caching with includes. I'll build it and do a load test and see what happens. I assume i can do farcry caching within an include object? Gav --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
