local helper application for remote database buffering

[Dr. Hawkins]

Aside from the "minor" issues of database creation and the web buffer
layer, I have my application talking to a remote server.

The lag, though, is quite noticeable, when tabbing from one field that
updates to another.

Would it make sense to stash the fields used on a card into a local
sqlite database, save to that, and have a second standalone monitoring
the buffer and doing the updates?  I know that I can simulate
multi-threading with a delayed message, but that's still going to
freeze up the interface when it happens, won't it?

-- 
The Hawkins Law Firm
Richard E. Hawkins, Esq.
(702) 508-8462
HawkinsLawFirm at gmail.com
3025 S. Maryland Parkway
Suite A
Las Vegas, NV  89109