Content-centric networking (CCN) offers a promising platform for efficient content dissemination through its name-based transport model exploiting in-network caching, multipath forwarding, and multicast delivery. Unlike IP transport, which is separated from applications, the receiver- driven transport in CCN allows applications to flexibly determine the transport functionalities they prefer. To achieve high throughput and minimize latency, a couple of transport control methods using various types of request messages have recently been proposed, but it is still unclear how they can support massive applications in terms of both the application requirements and network performance. In this article, we investigate the effectiveness of three types of requests: "pipeline," "symbolic interest," and "any next packet," when they are used as the transport control scheme in a CCN network. We carry out several performance evaluations regarding the latency, bandwidth overhead, and forwarding state reductions, and identify the characteristics and best use cases of each type of request as well as the potential challenges.