we should let the connections after the db connection is ready
switched memory checker to mb instead of %
adding an incremental for database fetches; it can take too much memory, decreased the timing between requests in cosequence..
-we need a better management for running jobs hoever reubmitting is not an option; freemem is working, changed to a minimum of free Mb
why update if there is no job after droping it ?
reseting que from collection upon startup and just getting jobs to
it is more effective to mass update the que gotten from server, and we should avoid collision of updates; this can improve the status marking and the whole performance for the server
added more verbose errors for hndling bad returns and a validation when no jobs are to be done