- 16 9月, 2014 2 次提交
- 08 9月, 2014 1 次提交
-
-
由 丁劲犇 提交于
* database confirm method in different threads, maximum 5 seconds /each check * close current db connection when error take place.
-
- 06 9月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 05 9月, 2014 2 次提交
- 29 8月, 2014 1 次提交
-
-
由 丁劲犇 提交于
Simply add a logger class, with the help of which , develpers can re-direct qDebug(), qWarning(), qCritical() and QFatal(...) outputs to log files , instead of stderr.
-
- 20 8月, 2014 4 次提交
-
-
由 丁劲犇 提交于
Add a auto-join cluster method, as soon as the server node be started, a join-cluster approach will be taken.
-
由 丁劲犇 提交于
-
由 丁劲犇 提交于
-
由 丁劲犇 提交于
Add a thread-quitting cleaning method. when a thread is quitting, its finished signal will be caugth, so that , db resource class can clean the database connections belongs to this thread one by one. this method is very important in some situation, such as Qt-concurrent threading, threads will be created, deleted frequently.
-
- 18 8月, 2014 1 次提交
-
-
由 丁劲犇 提交于
* sloved multi-thread db access problem. the databaseresource class has been improved, for each thread, a thread-owned db connection will be cloned from main db connection.
-
- 15 8月, 2014 1 次提交
-
-
由 丁劲犇 提交于
a bug caused by m_currentBlock.constData() has been fixed. the pointer returned by this method will be unavaliable when the block has been changed.
-
- 30 7月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 08 6月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 03 6月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 02 6月, 2014 1 次提交
-
-
由 丁劲犇 提交于
There is still a problem in heavily-test.
-
- 01 6月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 18 5月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 11 5月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 09 5月, 2014 2 次提交
-
-
由 丁劲犇 提交于
const QByteArray & type paras, will cause lift cycle problems. using Value-pass instead. ---- QString, QByteArray supports ref-count and auto-delete , also, these classes support least-copying, deep-copy will only take place, when the data is about to be changed. so, in singnals and slots, using QString, QByteArray instead of const QString & and const QByteArray & , will not cause performance problem.
-
由 丁劲犇 提交于
-
- 08 5月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 07 5月, 2014 1 次提交
-
-
由 丁劲犇 提交于
Each server instance knows exactly how many clients each server currently have.
-
- 06 5月, 2014 3 次提交
- 05 5月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 03 5月, 2014 3 次提交
- 02 5月, 2014 5 次提交
-
-
由 丁劲犇 提交于
-
由 丁劲犇 提交于
When cross-svr network established, servers will exchange their clients uuid info. wen client log in, local svr will broadcast its uuid to remote svrs, when clients log out, its uuid will be broadcasted again. we have only one step left.--the real data hop.
-
由 丁劲犇 提交于
-
由 丁劲犇 提交于
-
由 丁劲犇 提交于
-
- 30 4月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-
- 29 4月, 2014 2 次提交
- 28 4月, 2014 1 次提交
-
-
由 丁劲犇 提交于
-