Constants in App or session

Targets Web
1

Wondering where to put the constants for db_name, db_host db_host etc? and why?
Is it correct to add these constants under Session when you expect multiple users to login each with different passwords and usernames?

2

If you are talking about constants, then anywhere. Properties though should be at the session level if they are going to be different.

3

Thanks a lot Wayne. Just started out with Web app so I appreciate it.

4

One more question…
So if I have

If mDb.Connect Then mIsConnected = True
etc…

Do I put ‘mDB’ and ‘mIsConnected’ as property of ‘Session’ and call it

If session.mDB.Connect then session.mIsConnected = true
etc…

5

Yes. That will create a seperate db connection for each session.

6

Awesome thanks Albin.

7

If I have a multiuser webapp do I have to add all properties to Session and call them that way? What about methods? I’m not quite sure. Is there some reading about this?

8

If methods are to be for each user, keep them in WebPages or Session. And do not use static, it would bleed to all sessions. Use properties if you need to keep a value between calls.

9

So if I have methods in a webpage, let’s say a method to delete and enable some textfields, this won’t affect another users who is logged into the same webpage and calling the same method, right?

10

Indeed. Each session instance has its own instances of WebPage, properties and methods onto them. Basically, the more encapsulation the better.

Don’t use global or app properties unless you want all session users to access them. Modules methods are alright, as long as they don’t use global or static properties.