I was more thinking like the drawing primitives used in OpenGL.
there you can specify points and vertices and surfaces and the board calculates the image..
you could do the same using X..
specify the location of the window, and all the texturing, and here you go...
i believe it allready works that way, you just need to avoid the really heavy stuff like patterns..
al the drawing is done in the X-server, and is accelerated by the directFB stuff.
It would work just like the X-extensions you could load on X-terminals to speed up the rendering of vector-graphics...
It all comes down to the acid test
summarised in this url: http://www.shingray.com/town/database.html
ACID stands for Atomicity, Consistency, Isolation, Durability....
It means that a transaction on your database (a select, insert, update or delete) is done and stays done without any side-effects on other running transactions.
As soon as you get in an area where you want to sell things( think E-commerce..:) ) you want a transaction to be complete or to be rolled back...
Oracle or DB2 (and I believe Postrgresql) offer such functionality to extremes...
mysql doesnt. period...
Re:Quantum Communications
on
Stop, Light.
·
· Score: 1
This is where heisenbergs uncertainty principle comes in... you can't measure the transmission (read-out) without affecting the transmission.
So when you have quantum communications which are eavesdropped on, _BOTH_ sides know it instantly because the quantumlink is disturbed
so far for the eavesdropping where eavesdropping is defined as listening to two parties without the 2 parties _knowing_ it...
Slashdot Mirror
I was more thinking like the drawing primitives used in OpenGL.
there you can specify points and vertices and surfaces and the board calculates the image..
you could do the same using X..
specify the location of the window, and all the texturing, and here you go...
i believe it allready works that way, you just need to avoid the really heavy stuff like patterns..
al the drawing is done in the X-server, and is accelerated by the directFB stuff.
It would work just like the X-extensions you could load on X-terminals to speed up the rendering of vector-graphics...
maybe make the X-server use DirectFB?
that way you can use the client-server stuff from X and the fast graphics of DirectFB...
best of both worlds?
(sounds a bit like OpenGL)
It all comes down to the acid test
summarised in this url: http://www.shingray.com/town/database.html
ACID stands for Atomicity, Consistency, Isolation, Durability.... It means that a transaction on your database (a select, insert, update or delete) is done and stays done without any side-effects on other running transactions. As soon as you get in an area where you want to sell things( think E-commerce..:) ) you want a transaction to be complete or to be rolled back... Oracle or DB2 (and I believe Postrgresql) offer such functionality to extremes... mysql doesnt. period...
This is where heisenbergs uncertainty principle comes in... you can't measure the transmission (read-out) without affecting the transmission. So when you have quantum communications which are eavesdropped on, _BOTH_ sides know it instantly because the quantumlink is disturbed so far for the eavesdropping where eavesdropping is defined as listening to two parties without the 2 parties _knowing_ it...