View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000638||savapage-core||[All Projects] General||public||2015-12-08 16:28||2016-08-01 20:32|
|Target Version||0.9.11||Fixed in Version||0.9.11|
|Summary||0000638: Add Smartschool Print Clustering|
|Description||IST: An organization may want to use multiple SavaPage/Smartschool instances on different sites (offices) to poll for specific job tickets that are directed to a specific site (e.g. by means of a specific tag in the job comment). However, concurrent polling to the same Smartschool account is not possible, because of the limit of one poll per 2 minutes for each Smartschool account.|
SOLL: Add a ProxyService to SavaPage that acts as single-point-of-API in a cluster of SavaPage Smartschool Nodes. For example, in a cluster of 10 SavaPage nodes, one (1) Master node is assigned the ProxyService role. The nine other instances do NOT send their requests to the Smartschool endpoint but to the Master Proxy. The Master Proxy carries out polling (in accordance with the two-minute constraint) and caches job tickets and PDF files for client node requests. The proxy has the same interface as the native Smartschool SOAP end-point.
Note: because, for updating the print job status concurrency is allowed, proxy clients will use the native Smartschool end-point for that purpose.
|Tags||No tags attached.|
|2015-12-08 16:28||rijkr||New Issue|
|2015-12-08 16:28||rijkr||Status||new => assigned|
|2015-12-08 16:28||rijkr||Assigned To||=> rijkr|
|2016-04-04 13:10||rijkr||Status||assigned => resolved|
|2016-04-04 13:10||rijkr||Fixed in Version||=> 0.9.11|
|2016-04-04 13:10||rijkr||Resolution||open => fixed|
|2016-08-01 20:32||rijkr||Status||resolved => closed|