In a more normal client-server architecture, initial requests are sent to a server, which then responds with the requesting data.

ie: give me file XYZ

With the FCast project, it seems like the bulk of the transmitted data is from the "client" to the "receiver"?

At least, that's what it sounds like from this description?

  The client [...] uses the FCast protocol to send media content
  to the receiver, such as a TV or media top box.

Is my reading of this wonky? :)

The client provides a pointer (usually a URI but I think they also support playlists) of what to play. The receiver then requests the actual content directly from that URI and plays it. I guess it sends some kind of ok/fail response back to the client when it's done that.

The receiver does not send requests to the client. The receiver is server-like in that it responds to client requests, but it's not like a file server, those responses don't contain media data. Their description could be clearer.

> the bulk of the transmitted data is from the "client" to the "receiver"?

This is not new or novel. See: SMTP