differences between external librtmp and ffmpeg builtin librtmp, what about librtmfp?

[ROBERT-MCDOWELL]

I just discovered a defect on ffmpeg builtin librtmp, I opened a ticket at ffmpeg bug tracker for this matter.
Description:

• builtin ffmpeg librtmp does not recognize sub applications int the URL path, for example
  rtmp://host:port/app/stream is ok but rtmp://host:port/app/subapp/stream is not ok althought it's a perfectly valid rtmp URL. External librtmp follows the specis and accept as many as possible sub applications needed in the URL path.

What about librtmfp? is it following the specs or has the same behavior of the ffmpeg builtin librtmp?

[thomasjammet]

Hi Robert,

Fortunately you can use any URL path with librtmfp and the ffmpeg builtin.

[ROBERT-MCDOWELL]

Thanks Thomas, Just a correction from my comment it is not sub application but sub instance.
I wil try your last librtmfp git asap.