[Red5commits] [1636] only sent "NetStream?.Publish.BadName?" if another client is publishing
jbauch
luke at codegent.com
Wed Jan 24 11:10:56 EST 2007
only sent "NetStream?.Publish.BadName?" if another client is publishing
Timestamp: 01/18/07 19:04:09 EST (6 days ago)
Change: 1636
Author: jbauch
Files (see diff or trac for details):
doc/trunk/changelog.txt
java/server/trunk/src/org/red5/server/stream/StreamService.java
Trac: http://mirror1.cvsdude.com/trac/osflash/red5/changeset/1636
Index: /java/server/trunk/src/org/red5/server/stream/StreamService.java
===================================================================
--- /java/server/trunk/src/org/red5/server/stream/StreamService.java (revision 1635)
+++ /java/server/trunk/src/org/red5/server/stream/StreamService.java (revision 1636)
@@ -252,5 +252,5 @@
IBroadcastScope bsScope = getBroadcastScope(conn.getScope(), name);
- if (bsScope != null) {
+ if (bsScope != null && !bsScope.getProviders().isEmpty()) {
// Another stream with that name is already published.
Status badName = new Status(StatusCodes.NS_PUBLISH_BADNAME);
Index: /doc/trunk/changelog.txt
===================================================================
--- /doc/trunk/changelog.txt (revision 1635)
+++ /doc/trunk/changelog.txt (revision 1636)
@@ -35,4 +35,6 @@
- fixed ClassCastException in "pendingVideoMessages" (Jira APPSERVER-14)
- calling "pause" with null argument works again (Jira APPSERVER-12)
+- "NetStream.Publish.BadName" is only sent if another client is already
+ publishing a stream
Note:
Diffs are chopped if more than 25k.
This is to get past the limit on the mailing list.
More information about the Red5commits
mailing list