Challenge Overview
Project Overview
Currently, TopCoder Competition Engine used a customized way for communication between the client side (Arena applet) and the backend listeners. We are planning to implement a Web-based Arena based Web Socket protocol.
Previously, we have run contests to build a standalone web socket listener, which provides a good solution by using the combination of socket.io (web client) and netty.io (server side).
We are continuing to support more features needed by the new Web-Based Arena.
Competition Task Overview
This contest is going to implement web socket messages during compile and test problem solutions in a SRM contest. You are expected to analyze the current arena applet, see what kinds of requests and responses are sending between arena applet and main listener. and port them properly for web socket listener.
General Approach
We'd like to make the web socket listener as a wrapper over the main listener, the main logic should be implemented inside the main listener, several code changes are already checked in github repositories (https://github.com/cloudspokes/app/commits/master).
You can learn from the changes needed.
Please check the https://github.com/cloudspokes/app/wiki/Connect-Web-Socket-Listener-to-Main-Listener as a base knowledge to connecting the web socket listener and main listener, and follow the same approach to implement, any improvement is welcome.
Please reuse existing functionality used in main listener as much as possible.
Compile/Test Solutions
After the Coding phase for a SRM started, members can open problem and start coding.
We'd like you to analyze the current process, and port related messages to web sockets - Please provide a documentation to describe the process including code reference.
You can start from https://github.com/cloudspokes/app/blob/master/src/main/com/topcoder/server/processor/ResponseProcessor.java
Here are the request and response for the existing functionality, but not complete, but it is good for starting point.
-
com.topcoder.netCommon.contestantMessages.request.CompileRequest
- com.topcoder.netCommon.contestantMessages.response.PopupGenericResponse (title = Compile Result)
- com.topcoder.netCommon.contestantMessages.request.TestInfoRequest
-
com.topcoder.netCommon.contestantMessages.response.TestInfoResponse
-
com.topcoder.netCommon.contestantMessages.request.TestRequest
-
com.topcoder.netCommon.contestantMessages.response.TestInfoResponse
- com.topcoder.netCommon.contestantMessages.response.PopupGenericResponse (title = Test Results)
Web Demo
In order to demonstrate your solution, you are expected to update the demo (provided in forum), to demonstrate similar use cases.
in order to prepare the data, you can use Arena applet to do other work.
The demo provided may be a little out-date (other contests in parallel). Winner will be responsible for merging the demo.
Winner Responsibility
Winner will be responsible to create pull request in final fix phase, and help with the merge.
About Code Base
For the code under /home/apps/dev directory, some are hosted in internal svn repositories, some are hosted in private repositories in github.
You can check Source Code Management For TopCoder Competition Engine - TopCoder Wiki
For SVN Access, please send request to support@topcoder.com, For github access, please post your github account in forum to ask PM to grant you access.
Arena VM
Before asking your own VM, you need to have a public key on your profile before asking for the VM.
You can find more details on how to generate a key http://apps.topcoder.com/wiki/display/projects/Generate+SSH+Key and how to connect using it http://apps.topcoder.com/wiki/display/projects/Connect+Using+SSH+Key.
To use the Arena VM, please follow http://apps.topcoder.com/wiki/display/docs/Competition+Engine+VM+Setup
Currently, we moved several main projects to github, please check http://apps.topcoder.com/wiki/display/~fireice/Source+Code+Management+For+TopCoder+Competition+Engine
If you want to have local access to github, please create your own github account, and ask access in forum.
Final Submission Guidelines
Submission Deliverables
Below is an overview of the deliverables:
- Code Changes for the solution, please include the svn revision and git commit hash
- A complete and detailed deployment documented explaining how to deploy the application including configuration information.
Final Submission
For each member, the final submission should be uploaded to the Online Review Tool.