[Redback-devel] named nodes in URL, subnodes, error handling, config files

[Joshua M. <jo...@mi...>]

OK so that one's sorted. We now have named nodes by default, with the 
option of specifying the row ID using 'nodeId' in the URL. The syntax is:

http://example.com/doc/node/Welcome

or ...

http://example.com/doc/nodeId/348

... I have abandoned the 'virtual.html' (as well as the 'virtual.css' 
and 'virtual.js' at the end of CSS and JavaScript URLs).

My thoughts for the next steps with this system:

- Better exception handling. I moved the database with my website's data 
from a live server to my local box, and, when it found 'www.mirtec.net' 
as the fqdn instead of 'localhost', it gave me a fatal error. That's not 
good. Should drop out gracefully.
- Subnode handling. From the point of view of clean code, any node 
should be treated alike. From a performance point of view, much better 
to grab all data in one swoop (or as few as possible, maybe one to get 
the template html and another to get the prefs and related content). Of 
course I will have to go with the latter but I want to make it as clean 
as possible ...
- Config files. We need stuff like database user/password, path to 
Smarty, etc, in some kind of config file. PHP5 is much better at 
handling XML but I need to write this in PHP4 because the server I have 
my website on also has live websites for clients that would not be 
amused by any PHP5 teething troubles.

That's all from me, for now.

Josh


Joshua Mostafa wrote:

>Here is my current dilemma:
>
>I am a bit unsure about the way the Site object is currently generating
>URIs. At the moment they look something like:
>
>http://example.com/doc/node/423/virtual.html
>
>... or with a little more info (say, style info) they could look like:
>
>http://example.com/doc/node/423/style/58/virtual.html
>
>Now although this is good in that it doesn't show the technologies used
>(i.e. PHP) it is, according to an article (which I'll be damned if I can
>find again), bad in that it shows too much about the workings of the
>database (the IDs of the nodes) and too little about the content. So
>perhaps better would be to use:
>
>http://example.com/doc/all-about-fish/
>
>... and then styling information could be more explicit, eg:
>
>http://example.com/doc/all-about-fish/style/blue-theme/
>
>Of course this leads to naming conflicts, dealing with stupidly named
>nodes, etc ... I guess we could implement validation (based on unique-ness
>and absence of URL-friendly characters) and/or conversion of problemetical
>characters (urlencode(), maybe).
>
>It'll be good if we get this sorted before we try to host the homepage on
>redback.
>
>Thoughts?
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
>_______________________________________________
>Redback-devel mailing list
>Red...@li...
>https://lists.sourceforge.net/lists/listinfo/redback-devel
>
>  
>