[ grinder-Feature Requests-3526344 ] Replace console client API with RESTful web service

Feature Requests item #3526344, was opened at 2012-05-13 09:32
Message generated for change (Tracker Item Submitted) made by philipa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=368598&aid=3526344&group_id=18598

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Console
Group: None
Status: Open
Priority: 7
Private: No
Submitted By: Philip Aston (philipa)
Assigned to: Philip Aston (philipa)
Summary: Replace console client API with RESTful web service

Initial Comment:
The functionality of the console client API would be better as a REST web service.

There's no reason for it to be stateful, and there's a world of REST-aware clients that could do useful things with it.

Given the half-baked state of the client API, I plan to replace it completely. This will also allow the communication layer to be simplified (e.g. remove then "keep alive" stuff I added recently for bug #3521073; and the BlockingSender complexity), pathing the way for FR #3525230.

JSON would be a more sensible way to expose data to clients than building an object representation. This would help feature #3523611.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=368598&aid=3526344&group_id=18598

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/