VMDS: Perbedaan antara revisi
Konten dihapus Konten ditambahkan
kTidak ada ringkasan suntingan |
|||
Baris 13:
Konsep yang diterapkan ini dianggap sangat efisien karena data yang dikirim adalah data spasial yang bisa jadi sangat besar volumenya (sebagai contoh permintaan untuk menggambar ulang peta/''map redraw operation''). Dan dengan konsep inilah menjadikan VMDS sangat cocok untuk diterapkan pada pekerjaan besar yang melibatkan ratusan bahkan ribuan client yang bekerja bersama-sama.
<!--
==Support for long transactions==
Relational databases support [[Database transaction|short transactions]] in which changes to data are relatively small and are brief in terms in duration (the maximum period between the start and the end of a transaction is typically a few seconds or less).
VMDS supports long transactions in which the volume of data involved in the transaction can be substantial and the duration of the transaction can be significant (days, weeks or even months). These types of transaction are common in advanced network applications used by, for example, power distribution utilities.
Due to the time span of a long transaction in this context the amount of change can be significant (not only within the scope of the transaction, but also within the context of the database as a whole). Accordingly, it is likely that the same record might be changed more than once. To cope with this scenario VMDS has inbuilt support for automatically managing such conflicts and allows applications to review changes and accept only those edits that are correct.
-- >
==Pranala Luar==
| |||