It submits a HTTP HEAD request for the URL to the server the page is on, with the username and password supplied, so the server at the other end decides if you should be able to see the search results, thus saving you from having to faff around telling the google box who can get to what pages.
If it's the same as its big brother, then it boots up into RedHat Linux. You can watch all the usual bootup things happening, just not interfere with them, as the keyboard is ignored.
It does end up at a login prompt, but you're not given any usernames or passwords to access it.
I admin a full blown Google Search Appliance, the mimi's big brother.
If you want the specs: Dual Xeon 2.6GHz 12GB RAM 4 250GB HD's in RAID(something) with a hot-swap spare.
Never tried taking off the cover though, since we want to keep the warranty.
All of the money you pay is a license for the software on the box, the system itself is effectively free, so once the 2 year warranty expires, you've effectively got a nice powerful linux box for free. You can keep running the software, but without any support.
As for performance, this thing works great, we have about 250,000 pages that it can index, both public and private (and it can do searches cleverly checknig username/pasword to see if you should have access to certain results), and we've had nothing but positive responses from our users. The results come up quickly, they're the results people want, and the results that management think should be at the top, are at the top.
Ok, this article got me thinking, how could you make it so that a web-page could contain text, which COULDNT just be 'right-click, save as'ed, and how to make it still small to view the page.
Then I had an idea.. it's immensely horrible, but it's an idea.. it's not very practical, but solves some problems.
Generate a set of 60 or so small 2 bit images, for the letters, and punctuation you need. load them into one frame, so that the browser is liable to keep them cached. Then, when wanting to show a page, you generate s (unfortunately quite huge) HTML file with all the images used instead of letters. Problem, it'd be simple to just save the source, and pipe it through sed or something. Answer, dynamically replace the origional image in each position with the correct ones, through some horrificly complex bit of java script. This way the source you see doesnt match what's actually there. You just have the problem of huge HTML files to solve... and in the end it'd probably be easier to just make a single image for a page of text, and hope most people couldn't be bothered saving a few hundred images (and maybe run an OCR program over them)
Like all ideas... it's crap, but it might just work... not practical though.
In my opinion, the operating system is the part between hardware, and applications, which you cannot see. The operating system itself is the invisible layer, which provides a representation of the hardware to any aplication.
Sometimes conventions occur, whch when started are just a little joke... But after time they're almost an institution. Like here in out computer society, we have: MrChatterbox (A routing box) MrBusy (Primary login server) MrWorry (A box which we're always afraid is going to fall over) MrBounce (He goes up and down frequently) MrTall (He's got all the storage) ad so it goes on... What started as a joke, has evolved into a semi-resonable scheme. Keep the faith people, dont let *THEM* get their way!
This is actually a good point. Imagine someeon somehow manages to write a virus / trojan which somehow infects this. Suddenly a rogue process turns up, and it's invulnerable, and proceeds to randomly assasinate processes, and all you can do is sit there and watch it happen.
time for all of you old doom mappers out there to ressurect that map of where you work, so you can easily know which machine you're about to shutdown with that BFG you're holding...
How many of us can hold our hands up, and claim never to have put an amusing error message in a program, while writing it, and forget to take it out/change it to something 'understandable'
Slashdot Mirror
It submits a HTTP HEAD request for the URL to the server the page is on, with the username and password supplied, so the server at the other end decides if you should be able to see the search results, thus saving you from having to faff around telling the google box who can get to what pages.
If it's the same as its big brother, then it boots up into RedHat Linux. You can watch all the usual bootup things happening, just not interfere with them, as the keyboard is ignored.
It does end up at a login prompt, but you're not given any usernames or passwords to access it.
I admin a full blown Google Search Appliance, the mimi's big brother.
If you want the specs:
Dual Xeon 2.6GHz
12GB RAM
4 250GB HD's in RAID(something) with a hot-swap spare.
Never tried taking off the cover though, since we want to keep the warranty.
All of the money you pay is a license for the software on the box, the system itself is effectively free, so once the 2 year warranty expires, you've effectively got a nice powerful linux box for free. You can keep running the software, but without any support.
As for performance, this thing works great, we have about 250,000 pages that it can index, both public and private (and it can do searches cleverly checknig username/pasword to see if you should have access to certain results), and we've had nothing but positive responses from our users. The results come up quickly, they're the results people want, and the results that management think should be at the top, are at the top.
Give up with these tired old stories.
Yes it's april fools, we get the bloody picture. *enough*
Ok, this article got me thinking, how could you make it so that a web-page could contain text, which COULDNT just be 'right-click, save as'ed, and how to make it still small to view the page.
Then I had an idea.. it's immensely horrible, but it's an idea.. it's not very practical, but solves some problems.
Generate a set of 60 or so small 2 bit images, for the letters, and punctuation you need. load them into one frame, so that the browser is liable to keep them cached.
Then, when wanting to show a page, you generate s (unfortunately quite huge) HTML file with all the images used instead of letters. Problem, it'd be simple to just save the source, and pipe it through sed or something. Answer, dynamically replace the origional image in each position with the correct ones, through some horrificly complex bit of java script. This way the source you see doesnt match what's actually there. You just have the problem of huge HTML files to solve... and in the end it'd probably be easier to just make a single image for a page of text, and hope most people couldn't be bothered saving a few hundred images (and maybe run an OCR program over them)
Like all ideas... it's crap, but it might just work... not practical though.
Oh well, back to the old drawing board...
In my opinion, the operating system is the part between hardware, and applications, which you cannot see.
The operating system itself is the invisible layer, which provides a representation of the hardware to any aplication.
Sometimes conventions occur, whch when started are just a little joke...
But after time they're almost an institution.
Like here in out computer society, we have:
MrChatterbox (A routing box)
MrBusy (Primary login server)
MrWorry (A box which we're always afraid is going to fall over)
MrBounce (He goes up and down frequently)
MrTall (He's got all the storage)
ad so it goes on...
What started as a joke, has evolved into a semi-resonable scheme. Keep the faith people, dont let *THEM* get their way!
This is actually a good point.
Imagine someeon somehow manages to write a virus / trojan which somehow infects this.
Suddenly a rogue process turns up, and it's invulnerable, and proceeds to randomly assasinate processes, and all you can do is sit there and watch it happen.
time for all of you old doom mappers out there to ressurect that map of where you work, so you can easily know which machine you're about to shutdown with that BFG you're holding...
How many of us can hold our hands up, and claim never to have put an amusing error message in a program, while writing it, and forget to take it out/change it to something 'understandable'
+++ Out of cheese error +++ Redo from start +++