BeBits Information Developer Central Submit Application Your Account Web Links Contact Us
BeBits
Please support our sponsors!
gen_enqueuer
Talkback
 Go back to the gen_enqueuer page
 Post a new Talkback comment!
re: yes oversight
 By marcone - Posted on December 2, 2002 - 02:17:45   (#4540)
 Current version when comment was posted: 0.1
What happens when you monitor a large amount of files is that you run out of nodemonitors, UNLESS you use the magic functioncall to increase the limit. This is old hat, really. Look at how Tracker does it. And while the BeBook does call this an oversight, fact is that same BeBook also mentions how to work around it (without nodemonitoring, even). You didn't do this in your app, hence: programmer error :)

I also don't think the BeBook is necessarily correct in this case. The name of a file may have changed by the time you get the message, so you really should be looking at the device and node info, which won't change when the file gets renamed or moved.

Now, go and fix your app, and make a SoundPlay version while you're at it. ;)

yes oversight
 By SlimSCSI2 - Posted on December 1, 2002 - 15:39:30   (#4531)
 Current version when comment was posted: 0.1
Then what happens if you need to monitor over 4096 files (The maximum number of nodes you can monitor on the system)?. Not to mention that if you read the section of the be book that i pointed out it states...

"Notice that the B_ENTRY_REMOVED message doesn't tell you the name of the entry. This is an unfortunate oversight that will be corrected"

no oversight
 By marcone - Posted on November 30, 2002 - 01:57:04   (#4485)
 Current version when comment was posted: 0.1
There is no oversight in the Be API. It's pure programmer-error :)
If you want to know when a file goes away, you have to nodemonitor it (the file), and not the directory it is in. That's how (Open)Tracker does it.

RE: oversight?
 By SlimSCSI2 - Posted on November 27, 2002 - 12:40:04   (#4437)
 Current version when comment was posted: 0.1
The live Query support I am using is direct from the BQuery object described in the BeAPI. When the BQuery object detects a file was removed it sends a message. This message contains the drive and directory information for said file, but not the file name, leaving me no way of determining what file should be removed from the playlist.

For more information look at:
http://bang.dhs.org/be/bebook/The%20Storage%20Kit/Query.html
And search that page for "Entry Removed"

oversight?
 By marcone - Posted on November 27, 2002 - 11:14:03   (#4433)
 Current version when comment was posted: 0.1
What is this "unfortunate oversight" you speak of?

 
The Green Board
  Recent Downloads  -  # 632
Total Downloads  -  # 3,396
Total Views  -  # 3,112
User Ratings  -  N/A
  Misc. Info Management
MP3 Tools
MP3 Utilities
1.  QEMU - 9.62
2.  ScummVM - 9.50
3.  cpu_fix - 9.42
4.  Jukebox - 9.36
5.  Haiku AGP busm... - 9.35
6.  vim6 - 9.31
7.  Transmission - 9.27
8.  Beezer - 9.25
9.  BeeF - 9.25
10.  HandBrake - 9.24
1.  Ati Radeon Grap... - 363
2.  Realtek RTL8139... - 259
3.  BeOS 5 Personal... - 250
4.  ATI Rage 128 Pr... - 163
5.  USB Serial driver - 132
6.  Firefox - 118
7.  Broadcom 440x 1... - 102
8.  DjVu Viewer - 101
9.  S3 Trio 64 v2 DX... - 94
10.  Ensoniq AudioPCI... - 82
You are not logged in.
 Login or create an account...
Hosted by NetConnect

 
Unless otherwise noted, everything is copyright © 1999-2002 Fifth Ace Productions, LLC. All Rights Reserved.
For more legal trivia, take a gander at our
Legal Stuff page and our Privacy Statement.
Fifth Ace Productions