Students helping students, join us in improving Bored of Studies by donating and supporting future students!
Well that really is a social issue I guess. Mine were pretty bad. I think I wrote that them wanting to put it in a P plater and L platers car didn't give them real driving experience, like if they get their full license and use a car without it... and also like it could actually cause accidents if you swerve, trying to avoid something in the road and accelerate quickly - it will slow you down automatically and you'll get hit; the driver needs control. far fetched ideas but a bit tricky.ahh yes that's a good one
i wrote something stupid like a social issue which decreases speeding and job redundancy for cops..
Share your thoughts on the IPT exam.
I said it was to locate a specific page within the website.???For social ethical issues for GPS i did Privacy and changing nature of work for traffic police.
For the question with the URL.
For part III did u guys say it was a script or it was pointing to a file stored on the web server??
Ugh yes! By the end of the exam I was just sooooo over those questions!OMG those 6 mark collecting storing retrieving and whatever the fuck else destroyed me.
At least by and large the test was pretty fucken easy. It's always been full of ambiguous shit so, nothing new there.
For the music database, how many tables did everoyne have? I had 6: Song, Album, Artist, Customer, Genre, Purchase
LOL I couldnt think of shit so ended up writing about using it to calculate if you would get through a red light or not depending on your speed.. yeah, it was badI hated that GPS question, put this technology into another situation....
I bullshited the biggest bullshit out....I can;t remember what I wrote...
I put something similar to you, Customer, Song, Transaction and Genre... artist was in the song though...I had Customer, Song, Artist, Transaction and Genre, but I fucked up the schema thing with all the relationships and stuff
No, I am not talking about an anchor.no that content pointer thing you're talking about is an anchor which is represented by #
This is because of a bit of a misconception with what a URL actually is, probably helped by the days of static .HTML files and PHP scripts.
Traditionally, everything past the TLD is a pointer to a specific file. Say a blog post is located at example.com/blog/2009/oct/18/what-have-we-come-to. Without the use of fancy techniques, it would mean that there is a folder called blog, and in that is a 2009 folder, and in that a folder for every month, and in those folders ANOTHER folder for every day of the month. Clearly, this gets very complicated very quickly.
That is why web servers (such as Apache) and programming languages (such as PHP) invented URL rewriting. What that does is converts the said URL into something a bit more manageable, such as example.com/blog/articles.php?id=423. Here, a the articles.php script will use the provided post ID to look up the applicable post, then it will display the post, but the user would still see the URL as example.com/blog/2009/oct/18/what-have-we-come-to.
Another approach just scraps all this entirely. Everything past the TLD (in this case, /questions/56772/website-url-hiding-hiding-file) is merely a pointer to content, not necessarily a file. Some websites, such as Super User, a built using a MVC (Model-View-Controller) approach. Usually, this involves a list of URLs for a website, and maps them to the applicable functions and code in order to display that page. For example, Super User might look like this1:
This would most commonly be placed in a file by itself. I a common layout might be:Code:'superuser.com/' > displayFrontPage() 'superuser.com/questions/' > displayQuestionsList(sorted=default) 'superuser.com/questions/<QuestionID>/<QuestionID>' > displayQuestion(question= QuestionID)
1Please keep in mind that I have no idea how the controller works for ASP MVC (I am more of a Django guy), so this probably isnt that accurate. It is just an exampleCode:superuser/ controller.aspx (which contains the list of URLs and points to a view in views.aspx) views.aspx (which contains all the code for the superuser, such as displayFrontPage() and displayQuestion(question= QuestionID)) models.aspx (which contains information about the table in the database.)