Showing posts with label lotus perfomance. Show all posts
Showing posts with label lotus perfomance. Show all posts

Wednesday, December 16, 2009

Use JSMin when do web developing

I started to use JSLint and JSMin just couple weeks ago but now I have to say that everybody must use it.
Today I used JSMin and I have to say that In my case it saves ~22% of space (original size was 28kb and after minimization it was 22kb).

So, now when you are ready to put your JS libraries to productive server, use JSMin always! It is really cool (at least I think so :) )



Saturday, September 20, 2008

Platform Stats: Unable to obtain performance data. Please check Microsoft MSDN on how to enable performance data collection

I had this alarm on my home server (OS - XP, Domino 6.5.1IF1) where I made some testing. If somebody has the same thing then here you will find why it is so and how to disable this alarm.

why is it?
because you are running Domino on an unsupported OS (as clearly stated in the Platform requirements in the documentation/release notes).

XP is not supported, and there are known issues with it.
Supported Windows-based OSes for the Server are NT, 2000 and 2003. Not XP.

How to disable this alarm / notification?
Put this line in notes.ini platform_statistics_disabled=1 on Lotus Domino server.

Thursday, January 17, 2008

approches to transmit parametres from conf.document

usually every application has at least one configuration document which contains some information about our application and of course you should to use these data in your application.

1. @DbLookUp and @DbColumn every time
first way is to create a view where you can find this document (@DBLookUp or @DbColumn)and receive needed data each time when you want, but it's very slowly way and stupid, because there are a lot of dblookup will be.
2. transmit Id of config doc
there is one another way which I prefer to use is to transmit the id of conifg documents (using @dblookup or other ways) and then each time when you need some data, you can use @getdocfield(id; fldName)
3. collect all data in 1 field in profile and then use this field
Another one good approach is to save all data in configuration document in one field, for example [fldName1]fldValue1:[fldName2]fldValue2:[fldName3]fldValue3 and so on, after that you can load this field using just 1 @dblookup and then parse it and receive this data. This method I used very often too, but now I switch to method #2.

ok, i know that we can you real profile documents, but i don't like to do it, and I'm not able to tell you why is it so :)
but any suggestion and new idea will be appreciate !

Monday, January 07, 2008

perfect article about evaluate

Would you like to write fewer lines of code? Let Domino do some of your work for you? I doubt you answered no, but if you have, what the heck -- read on to see what you'll be missing! We're going to show you how to use the LotusScript Evaluate statement to easily include short and powerful formula language constructs within your LotusScript code. You'll save a lot of headache, and as much as twenty lines of code at a time! A single Evaluate statement can often replace many lines of complicated script, and in some cases, can do what is nearly impossible in native LotusScript... full article about evaluate

now I will twice think what is better to use LS of @.