Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Ok, so I'm hearing you want to be rid of some views as well? So, we are definitely building View-free results, very likely returning JSON. I think the pagination may be left in the hands of the programmer, at least to start.
currently I am creating java based web services via xsp. (Not dataservices but my own webservices using java backend classes) My frontend is an angular app.
Both (webservices and angular-app) reside in a NotesDatabase.
I want to get rid of all those views to fast get data from the database
1. hard-coding views for every single query (webservice) is annoing
2. Traversing views with a lot of documents by ViewNavigator is probablly the second best way to do..
Instead i imagin of a DQL with a pagable result set (similar to SQL) !?
This also may acffect node.js? Or do you expect the node.js app to cache the query results?
Hopefully now things are more clear. Thnx.
I'm not sure the venue being suggested here. Is it Node.js and domino-db? Back end classes? Web/REST API?
-John Curtis
Couldn't access the link.