Sorry for being so frank, but your mish mash of unrelated buzzwords and numbers shows that you obviously do not know that the scalability of your application is primarily determined by it's programmatic architecture.
Whatever hardware, language or frameworks you use, they will only provide you with access to a similar set of resources (in the sense of "a file", "a database row", or "a class member", not "a database", "a CPU", etc.), some of them limited, some not.
Whether these limitations impair scalability essentially depends the orchestration of their use, not the method of access.
that they have arrow keys? that they have round edges? that you carry a computer on a wristband?
No wait -- they have all these "cool" technical features, like Bluetooth, voice control and stuff. Too bad they're just design concepts that only exist in Photoshop imagery. And were done by people from Frog who dont know sh*t about the technical buzzwords they tag on their creations.
There are numerous approaches to the problem of making objects persistant. Unfortunately, people tend to think that once they serialize an object to disk, they have a database.
This assumption is incorrect. A real database meets the ACID criteria, and no persistence system is worth mentioning before it does so too!
Slashdot Mirror
Sorry for being so frank, but your mish mash of unrelated buzzwords and numbers shows that you obviously do not know that the scalability of your application is primarily determined by it's programmatic architecture.
Whatever hardware, language or frameworks you use, they will only provide you with access to a similar set of resources (in the sense of "a file", "a database row", or "a class member", not "a database", "a CPU", etc.), some of them limited, some not.
Whether these limitations impair scalability essentially depends the orchestration of their use, not the method of access.
-r
that they have arrow keys? that they have round edges? that you carry a computer on a wristband?
No wait -- they have all these "cool" technical features, like Bluetooth, voice control and stuff. Too bad they're just design concepts that only exist in Photoshop imagery. And were done by people from Frog who dont know sh*t about the technical buzzwords they tag on their creations.
cheers
There are numerous approaches to the problem of making objects persistant. Unfortunately, people tend to think that once they serialize an object to disk, they have a database.
This assumption is incorrect. A real database meets the ACID criteria, and no persistence system is worth mentioning before it does so too!
cheers
... can the Apple-supplied DVI-ADC adapter be used or is "DVIator" from Dr. Bott the only option? Any experience to share? Thanks Ralf