added BatchRequests class

Added a simple class to abstract the batch requests API.
The class works with a simple queue.
When the 'get' method is called, the request is being added to the queue
and a promise is returned.
There in an invetral that commits all of the requests in a batch once a given time and resets the queue.
When there is a response from the batch api, the requests that were queued are being iterated
and their matching promises are resolved or rejected based on the response from the API.

This allows the older way of sending ajax requests to the server work seemlessly with
the new batch api.
Changed the get helper to work with the batch api

Now the helper for making GET requests to the server works with the new batch api.
Removed first slash from API paths

due to an issue with the batch api, requests done to paths with a slash in the begining
will return 404 unless they are the first requests in the batch.

Until the issue is resolved, I have removed that slash from the api paths.
Claned up batch requests class
Added post and dlete methods to batch requests
added helpers for post called and delete calls with batch requests
removed debugging lines
added BatchRequests class

Added a simple class to abstract the batch requests API.
The class works with a simple queue.
When the 'get' method is called, the request is being added to the queue
and a promise is returned.
There in an invetral that commits all of the requests in a batch once a given time and resets the queue.
When there is a response from the batch api, the requests that were queued are being iterated
and their matching promises are resolved or rejected based on the response from the API.

This allows the older way of sending ajax requests to the server work seemlessly with
the new batch api.
Changed the get helper to work with the batch api

Now the helper for making GET requests to the server works with the new batch api.
Removed first slash from API paths

due to an issue with the batch api, requests done to paths with a slash in the begining
will return 404 unless they are the first requests in the batch.

Until the issue is resolved, I have removed that slash from the api paths.
Claned up batch requests class
Added post and dlete methods to batch requests
added helpers for post called and delete calls with batch requests
Merge branch 'add-batch-requests-support' of github.com:dzautner/osv-gui into add-batch-requests-support

Conflicts:
	Makefile
	osv/API/BatchRequest.js
	osv/API/FS.js
	osv/API/GraphAPI.js
	osv/API/JVM.js
	osv/API/OS.js
	osv/API/ThreadsGraphAPI.js
	osv/helpers.js
returned methods removed by accident on merge
post and delete helpers now use batch api
fixed hardcoded reqeust method
graphAPI now uses batchAPI
Added support for priority request in batch api

There was an issue that when deleting a trace from the count,
The delete request will be added to the queue after the get request.
That led to the response to send 'data' even though the trace is no longer there.
To fix the issue I have added an option to add priority request to the begining of the queue.
Assuring that they will execute first.
Made BatchRequest commit rate to by dynamic