rathinagiri wrote:That is so nice of you Roberto.
I am in the process of creating a simple connection/query mechanism for MySQL tables that can be easily extended to SQLite and PostgreSQL..
very interesting...
By the moment, I'll stop the development on websockets direction.
I'll borrow some of the code of the original HMGSCRIPT using synchronous AJAX and blending with current code.
This will have (theoretically) various advantages:
1. We could use any standard http server.
2. The server could be a Harbour based like the one included with the Harbour distribution (so, we could have server based Harbour routines).
3. Using synchronous AJAX (SJAX to be precise) our applications should be more inline with the xBase logic (no callbacks).
The question that many of you are thinking on is: Why to return to AJAX when websockets supposedly have a lot of advantages?
Well... because there is a big difference between knowing the path and walk it
I've walked websockets and I've learned that it has a lot of advantages and a lot of disadvantages too, the most important one, the lack of synchronous calls (I've tried to simulate without success).
Moreover, I guess that is very possible that the most effective solution be a mixed (Websockets and synchronous AJAX) one.
When some interesting happen, I'll post the code here!