edit · history · print

Main.HowDinoWorks History

Hide minor edits - Show changes to markup

April 08, 2008, at 01:38 PM by 81.188.94.80 -
Changed lines 65-71 from:

Interfacing with other applications such as (Hotelreservation, Stock, Sport, Time registration, credit control,…) are within our realisations

to:

Interfacing with other applications such as hotelreservations, stock, sports, time registration, credit control,… are within our realisations

April 08, 2008, at 01:37 PM by 81.188.94.80 -
Changed line 2 from:

Dino Technology, is an BRAND NEW application platform that uses a minimum of Windows and network bandwidth. No specific hardware needed like Raid controllers or dual Cpu’s servers.

to:

Dino Technology, is a BRAND NEW application platform that uses a minimum of Windows and network bandwidth. No specific hardware needed like Raid controllers or dual Cpu’s servers.

Changed lines 8-11 from:

We do not take in account polling systems that interchange data on regular intervals.

  1. Where your database is on a shared disk in the network and all clients access the data directly on this disk. Examples are softwares that use DBF, Paradox … databases. Each time the client needs data or wants to change it a LOT of data passes your network. The client always keeps needed databases and indeces open. This is typical for small networks : max 10 pc’s and 100mbit bandwidth if you want to work smoothly. This kind of databases get easily corrupted , example when you shut down a running pc in your network.
  2. Here you have an SQL server on a (dedicated) pc .The clients talk to this server with sql statements that are processed by the server. This server does the work and sends the result data back to the client. Examples are the DB2,Oracle,Pervasive and Ms Sql databases. Here you can build much bigger networks but the cost of licenses, maintenance and optimisation are high.
to:

We don't take polling systems that interchange data on regular intervals into account.

  1. Where your database is on a shared disk in the network and all clients access the data directly on this disk. Examples are softwares that use DBF, Paradox … databases. Each time the client needs data or wants to change it a LOT of data passes your network. The client always keeps needed databases and indeces open. This is typical for small networks : max 10 pc’s and 100mbit bandwidth if you want to work smoothly. This kind of databases gets corrupted easily, for example when you shut down a running pc in your network.
  2. Here you have an SQL server on a (dedicated) pc. The clients talk to this server with sql statements that are processed by the server. This server does the work and sends the result data back to the client. Examples are the DB2, Oracle, Pervasive and Ms Sql databases. Here you can build much bigger networks but the cost of licenses, maintenance and optimization are high.
Changed lines 14-19 from:

Both kind of networks are difficult to update and upgrade when drivers change or with program updates. If your database structure has changes in between versions often you have to run scripts and patches to update tables and fields and you will have to work on each pc in the network to get the job done.

Network troubles will crash the running software and take down your pc’s. You will be able to work again as soon as the problems are resolved .

Above systems really need 100mbit to work properly.

to:

Both kinds of networks are difficult to update and upgrade when drivers change or with program updates. If your database structure has changes in between versions, you often have to run scripts and patches to update tables and fields and you will have to work on each pc in the network to get the job done.

Network troubles will crash the running software and take down your pc’s. You will be able to work again as soon as the problems are solved.

The systems above really need 100mbit to work properly.

Changed line 31 from:

Dino hardly uses any disk access, because al the (most recently used) data is loaded into memory. Only modifications are written immediately to disk.

to:

Dino hardly uses any disk access, because all the (most recently used) data is loaded into memory. Only modifications are written immediately to disk.

Changed line 35 from:

In a dino-systems the online clients are automatically updated when changes arrive. The will update their screen immediately if needed . All clients appear to be alive.

to:

In dino-systems the online clients are automatically updated when changes arrive. They will update their screen immediately if needed. All clients appear to be alive.

Changed lines 38-42 from:

Simple low bandwidth networks like 10 mbit networks, Networks over the internet or VPN’s and Wireless networks are NO problem anymore.

With the easy setup a dino client can be reconfigured to act as a dispatcher.

Dino doesn’t need no drivers at all. Not even for the ticketprinters or other devices. Everything is integrated in only 1 exe-file.

to:

Simple low bandwidth networks like 10 mbit networks, Networks over the internet or VPN’s and Wireless networks are NO longer a problem.

With the easy setup a dino client can be reconfigured to act as a dispatcher.

Dino doesn’t need any drivers at all. Not even for the ticketprinters or other devices. Everything is integrated in only 1 exe-file.

Changed lines 44-45 from:

NO big installation programs to run !

to:

NO big installation programs need to run !

Changed line 51 from:
  1. Setup will ask you to resond to the following questions :
to:
  1. Setup will ask you to respond to the following questions :
Changed lines 58-64 from:

No IT knowledge needed, you only need to give a pc a unique name and ip-address . No need for domain controllers, or workgroups or file shares. Is there is a TCP/IP connection, Dino will do rest.

Everyday, during automatic maintenance, backup’s are created, files are being compressed and prepared for a new day. Version update’s are being pushed by the dino server towards the clients. Just install a newer zipped exe in a specific folder -> choose the moment of update (now or during maintenance) and the dino server will tell all of its clients there is a newer version and where they can download it. (the newer version can even be installend on external FTP servers with more upload facility)

to:

No IT knowledge needed, you only need to give a pc a unique name and ip-address . No need for domain controllers, or workgroups or file shares. If there is a TCP/IP connection, Dino will do rest.

Everyday, during automatic maintenance, backups are created, files are being compressed and prepared for a new day. Version updates are being pushed by the dino server towards the clients. Just install a more recent zipped exe in a specific folder -> choose the moment of update (now or during maintenance) and the dino server will tell all of its clients there is a more recent version and the place from which to download it. (the more recent version can even be installed on external FTP servers with more upload facilities)

Changed line 74 from:
  • Simple Hardware (Standard Pc Should do the job -> even in extreme situations)
to:
  • Simple Hardware (Standard Pc should do the job -> even in extreme situations)
Changed lines 80-81 from:

Example’s of hardware specifications of existing installations :

to:

Examples of hardware specifications of existing installations :

April 20, 2006, at 05:24 PM by 81.188.94.80 -
Changed lines 109-110 from:

http://wiki.etcworld.be/uploads/Main/eg4.jpg

to:

Eg4 :(Restaurant Group)

http://wiki.etcworld.be/uploads/Main/eg4.jpg
68 POS
Specs POS (Pentium 533, 256 mb, 40 gb)
1 Dino Server (Pentium 4 2 Ggz, 512 MB, statndard 80 GB IDE hard disk)
Interface with an SQL server and a shared database.
  • A till makes a request towards the dino server for a certain credit card
  • The dino server , accesses the SQL server
  • The dino server responds to the till’s request
April 20, 2006, at 05:22 PM by 81.188.94.80 -
Changed line 82 from:

(simple installations)

to:

(simple installations)\\

Changed lines 90-94 from:

http://wiki.etcworld.be/uploads/Main/eg2.jpg http://wiki.etcworld.be/uploads/Main/eg3.jpg

to:

Eg2:

http://wiki.etcworld.be/uploads/Main/eg2.jpg
3 POS (1 act’s a server)
specs POS (1GHZ celeron, 256 mb, 40 gb)
1 Pc (standard Pc) in the office, wich has full functionality (can even act as a till)

Extended installations
Eg3 :(airport)

http://wiki.etcworld.be/uploads/Main/eg3.jpg
48 POS
Specs POS (Pentium 400 mhz, 256 mb, 40 gb)
1 dino server + 1 Workstation (Pentium 4 2 Ggz, 512 MB, statndard 80 GB IDE hard disk)

April 20, 2006, at 05:20 PM by 81.188.94.80 -
Changed lines 80-81 from:

Example’s of hardware specifications of existing installations :


to:

Example’s of hardware specifications of existing installations :

April 20, 2006, at 05:09 PM by 81.188.94.80 -
Changed lines 80-83 from:
to:

Example’s of hardware specifications of existing installations :


(simple installations) Eg1:

Added lines 85-95:
http://wiki.etcworld.be/uploads/Main/eg1.jpg
3 POS (1 act’s a server)
Specs POS (1GHZ celeron, 256 mb, 40 gb)

http://wiki.etcworld.be/uploads/Main/eg2.jpg http://wiki.etcworld.be/uploads/Main/eg3.jpg http://wiki.etcworld.be/uploads/Main/eg4.jpg

April 20, 2006, at 04:58 PM by 81.188.94.80 -
Deleted line 1:

http://wiki.etcworld.be/uploads/Main/dinotechnology.jpg

Added lines 5-6:

http://wiki.etcworld.be/uploads/Main/dinotechnology.jpg

April 20, 2006, at 04:58 PM by 81.188.94.80 -
Changed line 2 from:
to:

http://wiki.etcworld.be/uploads/Main/dinotechnology.jpg

April 20, 2006, at 04:52 PM by 81.188.94.80 -
Changed lines 51-54 from:
	## are you client (default) or dispatcher 
	## if you choose client you fill in the name or ip of the dispatcher
	## Hit ok 
to:
  1. are you client (default) or dispatcher
  2. if you choose client you fill in the name or ip of the dispatcher
  3. Hit ok
April 20, 2006, at 04:51 PM by 81.188.94.80 -
Changed lines 3-10 from:

Distributed Intelligent Networking Objects.

In other words :
Dino uses its own way of sharing and saving the data across a network. Unlike other standard applications who are using the traditional way (sql, exchange, windows server, file sharing, ...), dino is very easy to setup an to maintain.

The system requirements are depending on the size of the installation, but generally speaking a 1 ghz pc, 256mb Ram and a hard disk off 20 mb are perfect to work with.

The two most important components for Dino are the CPU an the MEMORY.

to:

Dino Technology, is an BRAND NEW application platform that uses a minimum of Windows and network bandwidth. No specific hardware needed like Raid controllers or dual Cpu’s servers. No complicated and expensive server software (sql , windows server, ….). SUPER Easy installation . Dino is a new way of life for IT- people ;)

In the whole world you have 2 kinds of networks. We do not take in account polling systems that interchange data on regular intervals.

  1. Where your database is on a shared disk in the network and all clients access the data directly on this disk. Examples are softwares that use DBF, Paradox … databases. Each time the client needs data or wants to change it a LOT of data passes your network. The client always keeps needed databases and indeces open. This is typical for small networks : max 10 pc’s and 100mbit bandwidth if you want to work smoothly. This kind of databases get easily corrupted , example when you shut down a running pc in your network.
  2. Here you have an SQL server on a (dedicated) pc .The clients talk to this server with sql statements that are processed by the server. This server does the work and sends the result data back to the client. Examples are the DB2,Oracle,Pervasive and Ms Sql databases. Here you can build much bigger networks but the cost of licenses, maintenance and optimisation are high.

In both networks the client always takes initiative, they will not automatically be informed of data changes. Automatic screen updates only take place if the programmer placed a ‘refresh’ button on the screen or if he programmed a timer that refreshes the screen at regular intervals. >> Screen updates will always consume a LOT of network bandwidth.

Both kind of networks are difficult to update and upgrade when drivers change or with program updates. If your database structure has changes in between versions often you have to run scripts and patches to update tables and fields and you will have to work on each pc in the network to get the job done.

Network troubles will crash the running software and take down your pc’s. You will be able to work again as soon as the problems are resolved .

Above systems really need 100mbit to work properly.

Both systems rely on locking schemes that prevent concurrent changes to the same data. If badly programmed you end up with dead-locks. Only intensive optimization and testing will bring some speed on the clients.

DINO >>>> the FIRST REALTIME network

Dino = Distributed Intelligent Network Objects

Dino is a platform where data is distributed and synchronized on all systems in your network. The data is everywhere and every change is transmitted as a very small compressed object via the tcp-ip protocol. All systems in your network are equal. One system is assigned to act as a dispatcher (server), kind of an agent that controls the synchonization of data in your network.

Needed bandwidth to operate is reduced to an absolute minimum. Only when a change to some data is done on a client , the change will be transmitted to the dispatcher and the dispatcher will send it to all connected clients. Offline clients will catch up the changes as soon as they become online again. An offline client CAN continue to work without interruption.

Dino hardly uses any disk access, because al the (most recently used) data is loaded into memory. Only modifications are written immediately to disk. Dino NEVER keeps any file open. When Dino needs to read or write data it opens the needed files , reads or writes and immediately closes the files again. This is done in milliseconds. Dino uses its own data storage structure, which is highly compressed .

In a dino-systems the online clients are automatically updated when changes arrive. The will update their screen immediately if needed . All clients appear to be alive.

DINO will provide extreme performance on even standard Pc’s. Simple low bandwidth networks like 10 mbit networks, Networks over the internet or VPN’s and Wireless networks are NO problem anymore.

With the easy setup a dino client can be reconfigured to act as a dispatcher.

Dino doesn’t need no drivers at all. Not even for the ticketprinters or other devices. Everything is integrated in only 1 exe-file. Dino does NOT make changes to the registry. NO big installation programs to run !

A typical Dino installation works like this :

  1. unpack you new pc (2 min)
  2. Put it in your network by giving it a unique name and ip-address (5 min)
  3. put 1 exe on your harddisk (1 min)
  4. run the executable (30 sec)
  5. Setup will ask you to resond to the following questions :
	## are you client (default) or dispatcher 
	## if you choose client you fill in the name or ip of the dispatcher
	## Hit ok 

>> within 10 minutes you are up and running !!

No IT knowledge needed, you only need to give a pc a unique name and ip-address . No need for domain controllers, or workgroups or file shares. Is there is a TCP/IP connection, Dino will do rest.

Everyday, during automatic maintenance, backup’s are created, files are being compressed and prepared for a new day. Version update’s are being pushed by the dino server towards the clients. Just install a newer zipped exe in a specific folder -> choose the moment of update (now or during maintenance) and the dino server will tell all of its clients there is a newer version and where they can download it. (the newer version can even be installend on external FTP servers with more upload facility)

Interfacing with other applications such as (Hotelreservation, Stock, Sport, Time registration, credit control,…) are within our realisations

Resume

  • Simple OS (win2000 professional)
  • Simple Hardware (Standard Pc Should do the job -> even in extreme situations)
  • Simple Network layout (“if you can Ping -> you can DINO”)
  • Simple Setup and Maintenance
April 20, 2006, at 04:11 PM by 81.188.94.80 -
April 20, 2006, at 04:11 PM by 81.188.94.80 -
Changed lines 8-10 from:

Because of the high speed and flexibility,

to:

The system requirements are depending on the size of the installation, but generally speaking a 1 ghz pc, 256mb Ram and a hard disk off 20 mb are perfect to work with.

The two most important components for Dino are the CPU an the MEMORY.

April 20, 2006, at 03:38 PM by 81.188.94.80 -
Changed lines 6-8 from:

Dino uses its own way of sharing and saving the data across a network.

to:

Dino uses its own way of sharing and saving the data across a network. Unlike other standard applications who are using the traditional way (sql, exchange, windows server, file sharing, ...), dino is very easy to setup an to maintain.

Because of the high speed and flexibility,

April 20, 2006, at 03:35 PM by 81.188.94.80 -
Changed lines 3-6 from:

Dino is a technology wich

to:

Distributed Intelligent Networking Objects.

In other words :
Dino uses its own way of sharing and saving the data across a network.

April 20, 2006, at 03:23 PM by 81.188.94.80 -
Added lines 1-3:

How Dino Works

Dino is a technology wich

edit · history · print
Page last modified on April 08, 2008, at 01:38 PM