The w3Profile file tracks information about individual sessions. If profiling is enabled for an application in the w3Apps file, FlashConnect tracks each username and password supplied by the user. When the user starts the application again, FlashConnect automatically supplies the username and password so the user does not have to enter the information again. However, if a timeout period is specified in w3Apps, and the time period expires, the user must enter the username and password again.
|
Attribute |
Name |
Description |
|
0 |
Item-ID |
w3ProfileID value. |
|
1 |
w3Apps |
w3Apps entry used. Controls the remaining fields in w3Profile. There is one set of entries for each application tracked. |
|
2 |
w3Users |
w3Users entry used. |
|
3 |
Password |
Encrypted password. |
|
4 |
First.time |
Time this entry was first written. |
|
5 |
First.date |
Date this entry was first written. |
|
6 |
Last.time |
Time this entry was last used. |
|
7 |
Last.date |
Date this entry was last used. |
Maintaining the w3Profile file is recommended as it has a default modulo of 3, which can result in overflow if an application is not using anonymous users.
Disabling Cookies
U.S. Government regulations may prohibit the use of cookies for companies providing Web-based information and services for the U.S. Government. To disable cookies, the subroutine w3ProfileGetId must be modified to return a null Profile ID. If this is performed, WWW-IRUN does not send a w3ProfileID cookie to the browser and profiling is disabled for that application.
See Also