Oily Rag 1: Introduction: Difference between revisions
(New page: {{Uc nav oily rag 1}} '''UniServer 3.5-Oily Rag Introduction''' I am slightly saddened by the fact; Uniform Server 3.5 is the last in its series. The new model "four" series will eventual...) |
(No difference)
|
Revision as of 13:15, 29 June 2008
| Oily Rag: Be prepared to get your hands dirty. |
UniServer 3.5-Oily Rag Introduction
I am slightly saddened by the fact; Uniform Server 3.5 is the last in its series. The new model "four" series will eventually supersede it. However before that time comes with its boast of go-faster stripes, super plugins and 0-60 in the blink of an eye, I thought it worthwhile having an in-depth look at 3.5, sort of lift the bonnet and have a poke around.
Analogy
I use a car analogy because Uniform Server 3.3 is reminiscent of older cars where you can dive in, get your hands dirty, fine tune and bolt on a few goodies to make it uniquely yours.
Like a car you would not recast an engine block or camshaft, these are fixed components similarly DLLs and exe files are pre-complied hence are fixed components. In both scenarios you can tweak, move components around, add little extras, even move the air intake to act as a vacuum cleaner, this blows your engine apart as it sucks up a puddle of water.
Leads me onto component reuse, buried within 3.5’s architecture are some very elegant, standalone components just asking to be reused, perhaps in other projects however I am thinking more in terms of tweaks saving extra work when coding.
That dream
Ever purchased a brand new car, sat there looking at the dashboard wishing you could remove or add a new switch.
Not a chance for fear of devaluing the car, however take a look at 3.5 admin’s panel and reek your revenge; it won’t be devalued when you break it, just install a brand new one.
Opulence
Well if you are feeling opulent you can have a model 3.5 for every day of the week.
I purposefully neglected to state what the model refers to, thus giving me the opportunity to empathise that Uniform Server is much more than a web server.
Just get on with it!
If I were reading this article, by now I would be screaming! Show me something new and shut up. OK at least it’s not full of those irritating adverts.
|
|
So I lied! Could not resist it. |
|
|
|
At best they provide eye candy. |
|
After a time become so irritating | |
|
|
Result Click through Bandwidth is valuable don't waste it |
|
Title
For this series I could not think of a better title, oily rag seemed appropriate.
Anything you read in this section requires you to roll up your selves and get your hands dirty.
However I take no responsibility for any hair loss, blood dripping down walls (please bang your head against something else) or laptops that are hurled out of windows (could move to a basement flat).
Skills
Skills required, knowledge of CSS, HTML, be a competent programmer preferably in C++, PERL, PHP, MySQL and machine code and that’s only to service a car.
To complete any topic in this section I found copy and paste more that adequate.
For once in my life I will be very serious no mater what fancy titles or terminology you see it all boils down to one thing, manipulation of text files. If you know where to find these text files you can hack them to your hearts content and make them work for you.
Oily Rag - Content
3.5-Apollo problems and bugs
In keeping with the oily rag philosophy you will find detailed information on how to correct bugs in Uniform Server 3.5-Apollo.
The bug count has increased slightly I have consolidated these in a separate section 3.5-Apollo problems and bugs
Running 3.5-Apollo as a Service
I have retained this in the Oily Rag section because various pages require changing however installing and running see Running 3.5-Apollo Service remain easy.
Check out Combined bug fix it includes all pages that need changing.
ADDITIONAL TOPICS WILL BE ADDED - Move Over to Wiki
 |
Ric |