Displaying 3 results from an estimated 3 matches for "radiospi".
Did you mean:
radiospy
2004 Aug 06
3
a new directory service
> Again, it would be nice to be able to make this reasonably free form
> name/value pairs - one extra that has occurred to me is...
>
> icon_url - to let directoy listings jazz up their displays by permitting
> station logos (For speed reasons it's probably nicer for the directory
> server to manage teh icons locally...)
I'm trying to think of a good way to map
2004 Aug 06
2
a new directory service
I am not averse to making time-dependent information available. But it
does not fit in this model.
We have to change the model to accomodate time-dependent information,
and I'm not willing to use the model that has been use in the past,
which was to treat both types of information as identical and just
accept all the inconsistencies and problems.
And easy solution is to let clients query
2004 Aug 06
0
a new directory service
>> The Number of listeners *has* to remain in, it's up to the directory
>> server to do whatever they want with it.
>I disagree. It's fundamentally a different kind of data. It's
>time-dependent. All the other information is not.
>jack.
I'd just like to say that time-dependent information is very important to a
listener. Removing it from the directory would be