I am currently using a subscription license with Amazon load balancers for cupertino streaming. ELB has a way of doing sticky sessions via it’s own cookies, or application cookies. An application cookie would be much better (because it could be streaming session based), however Wowza doesn’t currently support adding cookies to cupertino streams. Please consider adding this functionality.
Wowza Server 3 has a way to set custom HTTP headers for HTTP streaming through the IHTTPStreamerSession.setUserHTTPHeader(String name, String value). You should be able to use this to simulate a set cooke. Cookie are just HTTP headers. You should be able to add a header that acts like a set cookie.
Cookie: name=value; name2=value2
streamerSession.setUserHTTPHeader("Cookie", "name=value; name2=value2").
http://en.wikipedia.org/wiki/HTTP_cookie
Charlie
I don’t think you need to set the cookie. My way will act as though the cookie is already set. Not sure what you are trying to do.
There is a Wowza 3 Preview that you can look at.
Charlie
great to hear. Is there any preliminary documentation on the api? Couldn’t find it on the site.
I assume you meant:
streamerSession.setUserHTTPHeader("Set-Cookie", "WMSSESSION=6666cd76f96956469e7be39d750cc7d9;expires=Sat, 08 Oct 2011 12:10:06 GMT;path=.example.com;domain=/");
Yup, “Set-Cookie” is what I needed. This is to support running wowza behind an amazon ELB with application cookie stickiness policy.
