Author Topic: Persistent Whois cache with out-of-bot upgrading (Read 85073 times)

Pharexys · « **Reply #30 on:** April 17, 2006, 02:26:20 pm »

hm atleast now works, and yes cofigured all.

But now i get this :

C:\bebot3.2\whoisbebot>php whois-update.php


================================================
0 http queries done!
0 entries in database modified!
0 entries in the whois cache!
0min 0sec total runtime!
================================================

C:\bebot3.2\whoisbebot>

Probly FC update Database i think:P

stonybg · « **Reply #31 on:** April 17, 2006, 07:08:43 pm »

Alreadythere can you modifay yor script to update members table?

Alreadythere · « **Reply #32 on:** April 18, 2006, 12:06:30 am »

Quote from: Pharexys on April 17, 2006, 02:26:20 pm

Probly FC update Database i think:P

Unlikely, as FC updates their server between 8-10 GMT usually.

You have to add entries to the table first, otherwise the script doesn't have anything to update. It does not go and pull a full mirroring of the FC databse.

Modify whois to use the cache, query a few people in different orgs, and run the script again - it should pull infos then.

Alreadythere · « **Reply #33 on:** April 18, 2006, 12:07:29 am »

Quote from: stonybg on April 17, 2006, 07:08:43 pm

Alreadythere can you modifay yor script to update members table?

It's not supposed to do that.

And it won't be possible anyways, as the UID is needed in the members table. And there is no way to get that from outside AO sadly. So you will always need a bot to update your members table.

stonybg · « **Reply #34 on:** April 18, 2006, 01:22:25 am »

but got truble with update members.....
and one way its out side ubdate in task command other its plugin ro make this
i teast all rosters plugin wit out any update im member info.....
can you help?

Wolfbiter · « **Reply #35 on:** April 18, 2006, 03:14:16 am »

I made roster_guild.php check the whoiscache: $result = $this->bot->db->select("SELECT * from whois where org_id='".$this->bot->guildid."'");
If it isn't empty(), I loop it, otherwise (some error with the db or whatnot) I use the old method. I've modified my roster way too much, else I'd post the file here.

Glarawyn · « **Reply #36 on:** April 18, 2006, 03:35:42 am »

You can get whois XML data from Auno as well, so it's possible to query whois cache, anarchy-online.com, and then auno if AO.com is down...

For Auno, only the URL changes...

http://auno.org/ao/char.php?output=xml&dimension=1&name=Auno

Alreadythere · « **Reply #37 on:** April 18, 2006, 11:43:25 am »

If you go an use the cache for member list updates, you should add an index over the org ids (or org names).
Otherwise searching in the table can take quite a bunch of time.

Khalem · « **Reply #38 on:** May 23, 2006, 07:59:36 pm »

Im currently adding the whois cache with some modifications to the BeBot 0.3 branch.
It will function fine standalone without out of bot updating, but can also be combined with out of bot updating

However, since i use character id's as the ID and for internal purposes, people cannot be added to the whois cache from outside the bot.

Im also doing a complete overhaul of get_site which will require minor changes to handle new return format just as a heads up.
The change in return format is to easier accomodate proper error messages, something which have been bugging me for some time.

The code should make it into the trunk sometime tomorrow if not earlier.

Alreadythere · « **Reply #39 on:** May 23, 2006, 08:36:43 pm »

I got an updated version of the whois module here.

It does include IDs (added them, haven't gotten around to use them yet though), and is a bit smarter then the last version I posted concerning which information to use and add.

The ID problem could be solved by adding a get_uid call each time a query is done which doesn't return an ID. Wouldn't be much overhead, and still work without any changes with the outside updating.

This version does work without outside updates too, would need a lower setting for whois_cache_persist_time though.

Khalem · « **Reply #40 on:** May 23, 2006, 10:24:28 pm »

The fallback to database version is a nice one wich i didn't think about.

I just commited the initial version of the whois cache. I'll add the fallback later

[Edit]
I should point out that i got slightly annoyed with the inconsistencies of some of the whois array names used in various places in BeBot and proceeded to alter a few of them, including the ones now given by the whois cache to make everything more consistent.

Alreadythere · « **Reply #41 on:** May 23, 2006, 10:44:53 pm »

Quote from: Khalem on May 23, 2006, 10:24:28 pm

I should point out that i got slightly annoyed with the inconsistencies of some of the whois array names used in various places in BeBot and proceeded to alter a few of them, including the ones now given by the whois cache to make everything more consistent.

Hehe, yes, too many people doing their own stuff.

I think I took the array out of the original whois function.
Not that it really matters, calls just need to be adapted once for consistency.

Alreadythere · « **Reply #42 on:** May 24, 2006, 09:54:29 am »

Just one question - why didn't you keep whois in it's own module?

Modules can be kept up-to-date easier, and the way I see it, the core modules are modules the bot depends on anyways.

Khalem · « **Reply #43 on:** May 24, 2006, 02:25:44 pm »

Main reason is that i consider the actual function of the whois lookup to be a completely integral part of the bot equal to the other core functions in Bot.php.
As so many modules depend on it, it made sense that it be a bot -> function.

I agree though on the easier to update argument, especially if you want to use a customized version of it. On the other hand though the actual whois lookup should rarely ever change except when Funcom changes XML aside from functional enhancements like smartening it up a bit.

Im open to feedback of course on any counts

Alreadythere · « **Reply #44 on:** May 24, 2006, 02:58:17 pm »

Yeah, I don't expect that function to get changed either tbh.

I'm just no friend of needless bloating up of the Bot class. Even though I've done it with my settings functions too. But going to post a core/Settings module for those functions soon.

Main reason I posted it as module was the either upgrading in the old bot.

Author Topic: Persistent Whois cache with out-of-bot upgrading (Read 85073 times)

Pharexys

Re: Persistent Whois cache with out-of-bot upgrading

stonybg

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

stonybg

Re: Persistent Whois cache with out-of-bot upgrading

Wolfbiter

Re: Persistent Whois cache with out-of-bot upgrading

Glarawyn

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Khalem

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Khalem

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading

Khalem

Re: Persistent Whois cache with out-of-bot upgrading

Alreadythere

Re: Persistent Whois cache with out-of-bot upgrading