This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
brainstorm
Jean-Guilhem Rouel edited this page Feb 24, 2016
·
2 revisions
Concerning the roadmap defined here :
- Might break the multithreading architecture used currently
- We could do local multithreading depending on the conditions
- For the recursion -> add a checkbox on the tasklist for the user
- Simplying the file format? Wasn't it already done?
-> [JG] IIRC, no. Contracts have been simplified but not the default observers' output. See milestone:"Simplify observer's output"
- Pain in the ass but why not! i'm fond of JUnit
- OK to do, don't know well how yet
- Repair the text fields parameter for the tasklist
- Add an option with text fields to enter the information
- Maybe ask for the type of protection with list of possible authentication (HTACCESS, ...)
-> [JG] We only want HTTP Auth as other ones may imply the use of cookies, session headers, ... See http://jigsaw.w3.org/css-validator/validator?uri=http%3A%2F%2Fwww.w3.org%2FTeam for example
- Need to know what is unsupported by jigsaw with the previous developer team
-> [JG] The tests I ran during my internship pointed out Jaxb as the culprit (more precisely, xml namespaces were managed in a different way on Jigsaw). Note that Yves would like to see Jaxb replace by something faster and more efficient
- Maybe adapt the code in order to make it work under jigsaw
- What about XGEN by CommerceOne ? Opensource and happen to be faster See there --->http://www.xml.com/pub/a/2003/09/03/binding.html
- We talked about it with olivier and might work with a designer team if the project goes well and works well :)
- Enhance the poor translation in french mainly :)
- Enhance the error handling for the final user (no more java exception)
Use an extra layer of security with two factor authentication (2FA) when logging into google