An amazingly useful application, I must say. Ever so much more
convenient than having to use iprelay to set up a squashed tunnel. ^.^
The problem is, as I believe you mentioned elsewhere, that if a flash
player initiates a connection after the page is loaded, then it will
not go through sloppy. Normally it is not a big deal, but now that I
have been commissioned to make an FLV stream player, it is somewhat
necessary. I figured, since I controlled the connection, I could test
it locally by pointing Sloppy to the Streaming Media Server and point
the SWF to Sloppy. The Problem? Sloppy's GUI prepends http:// to
everything. So I figured I would just use the CLI version, but then
that returned:
Failed to start Sloppy: java.net.MalformedURLException: no protocol:
or
Failed to start Sloppy: java.net.MalformedURLException: unknown
protocol: rtmp
Needless to say, I am at a standstill until I figure this out. My next
step is to poke around in the source code, but I figured I would post
here a) if someone already knew the answer, they might save me the
work, b) if I find the answer, I can post it for anyone else who might
need it, but most of all c) I really do not trust my ability to solve
this ^^'
Unfortunately Sloppy does mess with the HTTP request it passes on to
the real server. As such, it's built just for HTTP.
Having looked a the code -- and SlowProxyThread.java [1] in particular
-- we only do HTTP, but I don't see why we can't detect that you're
asking for non-HTTP and just do a bottlenecked-pass through of that
protocol. I don't know if it'd work as I'm not familiar with the
behaviour of RTMP, but it could be tried.
> An amazingly useful application, I must say. Ever so much more
> convenient than having to use iprelay to set up a squashed tunnel. ^.^
> The problem is, as I believe you mentioned elsewhere, that if a flash
> player initiates a connection after the page is loaded, then it will
> not go through sloppy. Normally it is not a big deal, but now that I
> have been commissioned to make an FLV stream player, it is somewhat
> necessary. I figured, since I controlled the connection, I could test
> it locally by pointing Sloppy to the Streaming Media Server and point
> the SWF to Sloppy. The Problem? Sloppy's GUI prepends http:// to
> everything. So I figured I would just use the CLI version, but then
> that returned:
> Failed to start Sloppy: java.net.MalformedURLException: no protocol:
> or
> Failed to start Sloppy: java.net.MalformedURLException: unknown
> protocol: rtmp
> Needless to say, I am at a standstill until I figure this out. My next
> step is to poke around in the source code, but I figured I would post
> here a) if someone already knew the answer, they might save me the
> work, b) if I find the answer, I can post it for anyone else who might
> need it, but most of all c) I really do not trust my ability to solve
> this ^^'
|
