John Jacobsen is a network administrator. He's responsible for maintaining the computer systems at the IceCube Laboratory in Antarctica. This page has a link to a 10-minute interview with him, explaining the difficulties of very remote access.
NEW COURSE - LEARN XPAGE DEVELOPMENT! Learn how to develop XPages with TLCC's new course, Developing XPages using Domino Designer 8.5. Learn XPages at your own pace and at your place. An expert instructor is a click away if you need help. Not just a collection of sample exercises, Developing XPages Using Domino Designer 8.5 is a complete and comprehensive course that will give you a thorough understanding of this exciting new technology in Domino.
Here's a great tip and a great video series too! This tip is brought to you by TipsInTwo. If you haven't heard of Tips in Two, you should definitely check it out. They have plenty of great videos, a
When clicking on a tag in the tagcloud, this tagcloud should also be filtered with the selection(s). So the tagcloud should only represent the documents that match the selected tagS.
Top Idea Tags is then also an incorrect label.
If you want to clear the filter(s) just go back to the startpage.
The warning message you get when scheduling something outside your designated available times is ambiguous. It states "This entry conflicts with an existing entry on your calendar or your availability preferences. Create anyway?". The warning should differentiate between conflicts and availability settings. It should either be "This entry conflicts with an existing entry on your calendar." or "This entry is not within your availability preferences." depending on the reason.
It would be nice when doing validation in Xpages for radio buttons (group) that when you set the validators ---> validateRequired ---> message, it would highlight the field then to the side of the highlighted field, your message is displayed in red or whatever color you choose and/or have some method of being able to display a message box to the user (easily) like other fields in Xpages. It would just be more visible to the user.
Classically, disk saturation (thrashing caused by page faults or long disk queues) are the main cause of poor server performance. Even in the most intelligently designed systems, the recommended standard tasks (compact, updall, stats etc) are culprits for high disk usage.
Intrinsic fo the philosophies of running high-intensity tasks (scheduled agents, system processes) that is demonstrated in the documentation, is the basic limitation that some servers/applications are 24-hr in nature.
Even on such systems, compact, updall etc are important, however are LESS important than server responsiveness (eg a global SAAS web application).
Given that disk (and sometimes processor) bottlenecks are the major cause of service degradation, it would be NICE to be able to prioritise tasks. EG, in the SAAS example, nHTTP would be given priority and / or, background "backburner' tasks such as compact should be able to be throttled at certain thresholds (eg less timeslices when certain thresholds are reached by the overall system).
GetThreadInfo is great for error handling. It would be great to extend with a parameter "LSI_THREAD_CALLSTACK" which records the subroutine/function call history. This would show the path code took before erroring out. This would also help identify infinite loops.