Antclick + Object Cache
Hello,
following situation:
we have designed some php-scripts to work with antville:
-
a register script, where user can register themselves and admins can approve them, if there nick & email is ok (with password-generation) - therefore we use a table AV_NEWUSER, while approving a user he is added to AV_USER
-
a user-deleting script, where admins can delete users from antville... it sets all referenced storys etc to user "Guest" (-> no errors)
--> that means, the scripts have direct access to the mysql-database, without using antville
After approving, the new user does not appear in antville's user-list. After deleting a user, he is still at the user-list. The change takes minutes up to hours or needs a cmplete restart of antclick before the result is visible in antville. For approving users it is an unwanted "feature", because they should be able to login immediatly.
Our questions: How often antclick updates its objects from the database? Is it effected by a "garbage collector"? (We know, that JAVA uses a garbage collector.) Can we change a setting anywhere, so that actualisation would happen more often?
please help! thx..
sorry for this bad english, we're german & austrian ;)
kinomu Verwaltung
The two mailing lists seem to be a better place for this sort of problem.tobi Verwaltung
the application server helma which is behind all of antville/antclick's capabilities updates its object cache just as needed. e.g. when an object was changed from within helma (ie. in antville) it will be reloaded to the cache memory (or invalidated in helmaspeak).
if another application (like your php script) modifies the database antville is connected to, helma won't notice these changes unless you "manually" invalidate the object (or the collection containing it), which certainly happens when you restart antclick (but there are simpler ways, too).
most likely there is a solution to your specific problem but it's rather helma- than antville-related and i'd prefer the discussion not to take place here. thus, i kindly ask you to forward your question to either one of the two helma mailing-lists.