search for: listener_joined

...r.com/station-aac > > http://west.icecastserver.com/station-aac > > 3) Client makes request to icecast and the url auth sends the request > for auth back to the app where we log the session id again from the > header as starting a session > > http://webapp.com/listener_joined > > 4) App returns the ok to icecast and the server begins the stream. > > 5) If the client drops and reconnects to icecast it already has the > session in the header for the icecast path and we're good to go. Yes. > As far as source goes, since im sending the client to...

I have an app that I've built that leverages the auth functionality of icecast2 to track when listeners are added to the stream and monitor what they listen to. I've ran in to an issue where if a listener disconnects for a few seconds then reconnects, I track them as a new user. I can't track by ip cause there may be a few people listening from the same public ip. In the docs I