Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

Re: Re: My favorite other on-line community is...

by Wally Hartshorn (Friar)
on Feb 03, 2003 at 19:59 UTC ( #232383=note: print w/replies, xml ) Need Help??


in reply to Re: My favorite other on-line community is...
in thread My favorite other on-line community is...

re: "VikingMUD, since 1993, and before that, IgorMUD, since 1991. My most precious community. By far the least amount of traffic, but I've spend 1354 days there. That 1354 * 24 hours being online there."

(Doing some math here...) If I understand correctly, you are saying that over the last 12 years, you have spent an average of 7-8 hours per day on these MUDs. Is that correct?

*blink* And you're employed? And you sleep? *blink*

Wally Hartshorn

(Plug: Visit JavaJunkies, PerlMonks for Java)

  • Comment on Re: Re: My favorite other on-line community is...

Replies are listed 'Best First'.
Re: Re: Re: My favorite other on-line community is...
by castaway (Parson) on Feb 04, 2003 at 10:17 UTC
    Thats nothing unusual. Bear in mind that most muds continue to count time even if you are idle, and a lot of people just leave themselves logged in over night. (Not that I'm saying Abigail does this, but some of those hours are bound to be idle ones.)
    (I started in 1993 and have probably around a 1000 days online-time, if I add all the various muds together that I played (averaging about 150 days on each one..))

    C.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://232383]
help
Chatterbox?
[ambrus]: what push_write thing? I don't think you need that. that's implemented generically by AnyEvent::Handle
[Corion]: ambrus: Yeah, that's what I think as well. But you give me an idea, maybe I should start with implementing the timer, as that should be far simpler and with fewer edge-cases/nasty interaction than the file watcher
[ambrus]: You only provide the watcher part that tells when the handle is readable or writable, not the actual writing and reading.
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (8)
As of 2016-12-08 12:21 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.