Future of Totaljs

[ghost]

Peter,

Can you share your vision about the future of Totaljs and your challenges for 2018 ? What are the next enhancements for the version 3.0 ?

Thank you for your work :)

[petersirka]

Thank you! Year 2018 will be mainly about Total.js products.

Total.js framework:

• add new features which will make the development more efficient
• improve performance
• improve stability
• keep backward compatability but I want to remove older code
• improve docs
• extend community
• create an example for larger apps (with cluster and redis)
• create an example with LDAP
• create new tutorials about creating apps

Total.js products:

• new version of Eshop and CMS
• update HelpDesk app
• improve Total.js Messenger
• create some free apps for OpenPlatform
• create NoSQL embedded wrapper for MongoDB or PostgreSQL
• improve docs for products on Wiki
• add new Flow/Dashboard/Flowboard components

jComponent:

• create new components
• extend community
• improve wiki

Other:

• Find a hosting partner
• Find partners
• Find money for larger development
• Update homepage

So we will see. I want to continue, I love it. My work is my hobby.

[ghost]

Check this link for the hosting : https://zeit.co/ Big Big program... Good luck

[ghost]

Do you integrate some security enhancements for 2018?

[webdesus]

Work on security is ongoing always. What kind of integration do you talking?

[petersirka]

My question is same.

[ghost]

I talk about the Helmet module : https://helmetjs.github.io/ Do we have the same security process with Total.js ?

[webdesus]

Hard question but i think it's redundancy... better using set header as string. Helmetjs has good docs about problems which might happen. But using their library I would not.

But if you have another oppinion. You can write something like this:

const nocache = require('nocache')();
const frameguard= require('frameguard')();

F.on('request', function(req, res) { 
    nocache(req, res,()=>{
        frameguard(req, res, ()=>{});
    }); 
});

Not tested, but should work.

[ghost]

Thank you very much

[webdesus]

Some modules helmet so big, and execute very more logic. I would advise to examine helmetjs site and write once own definition file with your headers as strings. Then if you create new project you can copy this file. You should get somethink like this:

F.on('request', function(req, res) { 
    res.setHeader('Surrogate-Control', 'no-store')
    res.setHeader('Cache-Control', 'no-store, no-cache, must-revalidate, proxy-revalidate')
    res.setHeader('Pragma', 'no-cache')
    res.setHeader('Expires', '0')
});