![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
do you want to ask me? |
#3
| |||
| |||
|
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
|
ok there's not that many places that have machines that use 'the pick operating system' still .. but it does still run on a LOT of machines generally running universe or unidata or some other variant and it communicates very well, for once people are making money out of it it's a slow burner it's still smouldering people who know pick can earn a lot of money |
#7
| |||
| |||
|
|
and I love that the sql trend seems to be losing ground to the embedded database |
|
Terminal Services by Microsoft (after Citrix did the ground work). hmm have we seen this model before? ;-) |
#8
| |||
| |||
|
|
jimh wrote: and I love that the sql trend seems to be losing ground to the embedded database This makes no sense. SQL is a data retrieval/manipulation language supported by many RDBMS. Embedded database usually means that the database engine is "embedded" within an application, not running as a separate entity. The two are not related. |
|
I.e. Both MS SQL Server and MS Access can use SQL as a means of retrieving information. SQL Server is a stand-alone database engine to which clients connect. MS Access is an embedded database. It does not run on it's own. Clients cannot connect to an instance of Access running autonomously. Terminal Services by Microsoft (after Citrix did the ground work). hmm have we seen this model before? ;-) Well, not really. Until Citrix did it, I don't *think* anyone had come up with a way to run multiple user sessions of a Windows operating system to a terminal type client. If you're implying that Pick was unique in its terminal to server setup, I believe that's pretty much how all mainframes and micros of the era worked. Pick surely didn't invent it. |
| -- Kevin Powick |
![]() |
| Thread Tools | |
| Display Modes | |
| |