Challenge Overview
Welcome to the PoC - Electron App Preconnect Challenge.
1. You need to investigate how HTTP preconnect can be incorporated into Electron (https://electronjs.org). As start point you can use this Github issue https://github.com/electron/electron/issues/16476
2. In this challenge you will debug the issue and will provide a PoC fix for following issue: When a page provides a preconnect resource hint via a response header or link tag using an Electron App, it should preemptively preconnect to the specified domain.
3. You will need to provide a PoC solution that describes the solution in a Word document with any diagrams to help explain, as well as some minimal source (snippets) code to back your solution.
4. You will need to provide a document with Test/Example cases to support the solution will work.
5. You are not required to provide a full solution of the problem but we need:
Challenge Objectives
- In this project we are aiming to fix one issue of the Electron App that doesn't support HTTP Preconnect. A useful resource to understand preconnect is here https://www.keycdn.com/blog/resource-hints.
- This will be the first of a 2 challenge series that will be available for the community.
Challenge Background
- Our client make use Electron for one of their internal applications.
- It has requested Topcoder to help resolve a preconnect issue for the core Electron project owned by the open-source community.
Technology Stack
- C/C++
- Javascript
Individual Requirements
1. You need to investigate how HTTP preconnect can be incorporated into Electron (https://electronjs.org). As start point you can use this Github issue https://github.com/electron/electron/issues/16476
2. In this challenge you will debug the issue and will provide a PoC fix for following issue: When a page provides a preconnect resource hint via a response header or link tag using an Electron App, it should preemptively preconnect to the specified domain.
3. You will need to provide a PoC solution that describes the solution in a Word document with any diagrams to help explain, as well as some minimal source (snippets) code to back your solution.
4. You will need to provide a document with Test/Example cases to support the solution will work.
5. You are not required to provide a full solution of the problem but we need:
- Full details on the issue (why is it happening)
- What source code should be changed?
- And what needs to be changed (snippets)
Final Submission Guidelines
- Word document describing the PoC fix solution.
- Word document with test cases to verify the solution when fixed.