If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Create smart "Data Manager" for ChatZilla objects

NEW
Assigned to

Status

Other Applications
ChatZilla
--
enhancement
12 years ago
8 years ago

People

(Reporter: James Ross, Assigned: Robert Ginda)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
I had a bit of an interesting idea the other day, regarding various bugs we have. Why not have a Data Manager that helps coordinate fetching data asyncronously?

For example, bug 273505 would like the away message of a user when the mouse of hovered over them in the userlist. This data can be fetched via a /whois command, but that need not be exposed. With the Data Manager, the code could simply do this:
  userObj.getData("awaymsg", callbackFn);

Then, the Data Manager (which would be used to make sure nothing silly happens) would check for cached data (maybe), and then make userObj issue whatever is necessary for "awaymsg" (the objects would define what data properties they have, and only they would know how to fetch it). Then, the object would capture the reply, make sure not to display it (the DM would be able to tell the object that someone requested the data, if the object wasn't sure), and finally pass it to the DM for the callback (and maybe caching).

It sounds more complicated than it is; really, each object would just need to be able to identify data that was requested, and pass over to the DM. This would also be potentially great for commands that show async data (like /whois), because the callback could make sure to always use the correct view for display. :-)

P.S. A different name for this manager wouldn't hurt.
(Reporter)

Updated

12 years ago
Blocks: 319199

Comment 1

11 years ago
latentReplyManager? Except that sounds way too eloquent for a variable name...
(Reporter)

Updated

8 years ago
QA Contact: samuel → chatzilla
You need to log in before you can comment on or make changes to this bug.