AW: AW: [icecast] final question: how many mountpoints can icecast handle ?

Andreas Gunzenhauser andrew at baselbiet.ch
Wed Nov 7 04:44:05 PST 2001



Hello Michael

damn, I was afraid of that, but thanks for lightening me up 
(although I am in complete darkness now, after having seen 
the light just some days ago..)

I'm looking into http streaming of the static files just now,
but I came to find that there is one huge drawback:

1. when sending the stream out with icecast/shoutcast 
   it would be possible to "push" the next song in, even 
   let the user influence this so that he could act like 
   when playing a CD, so he could go on to the next song etc 
   and request specific songs from his playlist. 

   Unfortunately, as it turned out, icecast is thought to 
   send a FEW source-streams to MANY users. What I want to do is send 
   ONE source-stream to ONE user, so it will be as many source streams 
   as there will be users.

2. When using http streaming, sending ONE static mp3 file to one user 
   works fine, apache can handle many such streams, but the user
   could then just have ONE file sent, then select the next and play it 
   etc -> so its again a computer-thing, no stereo-like interface that 
   even my mum could use when connected to the internet to look for songs, 
   add to playlist and let them be played by a continous stream.

Please excuse my ignorance but I don't know about a way to 
do such a thing to have a way to interact with the stream.

Anybody ?

best regards,

Andrew

> -----Ursprungliche Nachricht-----
> Von: owner-icecast at xiph.org [mailto:owner-icecast at xiph.org]Im Auftrag
> von Michael Smith
> Gesendet: Mittwoch, 7. November 2001 11:50
> An: icecast at xiph.org
> Betreff: Re: AW: [icecast] final question: how many mountpoints can
> icecast handle ?
> 
> 
> 
> >So problem is, if I wanted to handle, say 1000 streams,
> >I would need 200 Servers..this puts the concept a bit 
> >in jeopardy because that would push the cost of the service 
> >into astronomical..in comparison to handling, as I had planned 
> >until now, 500 individual streams per server.
> 
> Well, your calculations are a bit off here to begin with - the numbers
> here give 20 (or more) servers, not 200 or more. 
> 
> >
> >So I guess I'll have to wait until Icecast 2 for doing 
> >a real prototype of this.
> >
> >Just so that I get this right - if I have 1000 different on-demand 
> >streams (its on-demand radio from huge mp3-library for users) 
> >mountpoints are definitly the way to go, yes ? Or am I on 
> the woodpath ?
> 
> Really, you're on completely the wrong path here - there's a simple
> way to do this. Remember: icecast just serves content over 
> HTTP. If all
> you want to do is serve a static mp3 library to individual 
> users, seperately,
> then a web server (such as apache) is much better suited to 
> your needs.
> 
> This isn't to suggest that icecast CAN'T do this, but it 
> isn't really the
> most sensible approach.
> 
> Michael
> 
> 
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to 
> 'icecast-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No 
> subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
> 

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.



More information about the Icecast mailing list