Rev 1349 | Rev 1360 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 1349 | Rev 1350 | ||
|---|---|---|---|
| Line 1... | Line 1... | ||
| 1 | 1 | ||
| 2 | August 2023 planned: |
2 | August 2023 planned: |
| 3 | - Make a setting which rejects pages to proxy OIDplus (is this possible? What if the proxy does not send HTTP_X_FORWARDED_HOST?) |
3 | - Backup plugin: https://github.com/danielmarschall/oidplus/issues/18 |
| 4 | 4 | ||
| 5 | May 2023 planned: |
5 | May 2023 planned: |
| 6 | - Don't send "information object OIDs" (= Non-OIDs) OIDs to oid-info.com anymore |
6 | - Don't send "information object OIDs" (= Non-OIDs) OIDs to oid-info.com anymore |
| 7 | => 17 May 2023 mitigated at VTS internal side |
7 | => 17 May 2023 mitigated at VTS internal side |
| 8 | - In re Internet access: |
8 | - In re Internet access: |
| Line 24... | Line 24... | ||
| 24 | Unicode compatibility: |
24 | Unicode compatibility: |
| 25 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
25 | - [DONE] SQL Server needs nvarchar instead of varchar (works with emoji too) |
| 26 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |
26 | - [DONE] MySQL works with Unicode and emoji if collation is utf8mb4 |
| 27 | - [DONE] Access table structure works with Unicode |
27 | - [DONE] Access table structure works with Unicode |
| 28 | - PDO+MySQL: Unicode (with emoji) works, but PDO+ODBC+MSSQL and PDO+ODBC+ACCESS does not work, so it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
28 | - PDO+MySQL: Unicode (with emoji) works, but PDO+ODBC+MSSQL and PDO+ODBC+ACCESS does not work, so it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
| 29 | - ODBC+MSSQL and ODBC+ACCESS: Unicode deos not work. So it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
29 | - ODBC+MSSQL and ODBC+ACCESS: Unicode does not work. So it's ODBC's or ODBC-Driver's fault. Can we do something about it? |
| 30 | (Note: ODBC and PDO can save UTF-8, but then they are double-encoded in DBTool/Access/SQLManagementStudio. When you insert Unicode in DBTool/Access/SQLManagementStudio, then they show up as '??' in OIDplus) |
30 | (Note: ODBC and PDO can save UTF-8, but then they are double-encoded in DBTool/Access/SQLManagementStudio. When you insert Unicode in DBTool/Access/SQLManagementStudio, then they show up as '??' in OIDplus) |
| 31 | - ADO via OLEDB does not seem to support Unicode??? But it should! https://stackoverflow.com/questions/28311687/unable-to-retrieve-utf-8-accented-characters-from-access-via-pdo-odbc/28341697#28341697 |
31 | - ADO via OLEDB does not seem to support Unicode??? But it should! https://stackoverflow.com/questions/28311687/unable-to-retrieve-utf-8-accented-characters-from-access-via-pdo-odbc/28341697#28341697 |
| 32 | - [DONE] SRVSRV plugin is capable of Unicode and pile of poo Emoji. |
32 | - [DONE] SRVSRV plugin is capable of Unicode and pile of poo Emoji. |
| 33 | 33 | ||
| 34 | Exception Refactoring: |
34 | Exception Refactoring: |
| Line 88... | Line 88... | ||
| 88 | - Let users have their own settings. This could be achieved by the ###_config table, by having a key with the name scheme "<settingname>(<useremail>)". |
88 | - Let users have their own settings. This could be achieved by the ###_config table, by having a key with the name scheme "<settingname>(<useremail>)". |
| 89 | Example settings: |
89 | Example settings: |
| 90 | * Own color settings |
90 | * Own color settings |
| 91 | * Newly created OIDs: Always open, Never open, Ask (default) |
91 | * Newly created OIDs: Always open, Never open, Ask (default) |
| 92 | But what do we do if multiple users are logged in?? |
92 | But what do we do if multiple users are logged in?? |
| 93 | - "Download Backup" plugin (contains SQL backup, as well as everything inside "userdata" and "userdata_pub") |
93 | - "Download Complete Backup" plugin (contains a full SQL backup for all DBMS, as well as everything inside "userdata" and "userdata_pub") |
| 94 | - if a third-party plugin throws an exception in the init() method, maybe OIDplus should avoid loading the plugin? |
94 | - if a third-party plugin throws an exception in the init() method, maybe OIDplus should avoid loading the plugin? |
| 95 | - "hidden" alt ids which are not shown in the GUI, but can be used for reverse-Alt-ID ? (I believe we have excluded some AltIDs which are "not neccessary", e.g. an GUID already is a GUID and therefore does not need a Namespace GUID, or something like that) |
95 | - "hidden" alt ids which are not shown in the GUI, but can be used for reverse-Alt-ID ? (I believe we have excluded some AltIDs which are "not neccessary", e.g. an GUID already is a GUID and therefore does not need a Namespace GUID, or something like that) |
| 96 | 96 | ||
| 97 | RDAP: |
97 | RDAP: |
| 98 | - Extend handle404() to handle more things required by the RFC, as well as more object types |
98 | - Extend handle404() to handle more things required by the RFC, as well as more object types |