我目前正在針對(duì)返回批處理結(jié)果的 xml 服務(wù)進(jìn)行編寫。我目前有以下幾點(diǎn)：type QueryEnvelope struct {    XMLName xml.Name   `xml:"http://schemas.xmlsoap.org/soap/envelope/ Envelope"`    Body    *QueryBody `xml:"http://schemas.xmlsoap.org/soap/envelope/ Body"`}type QueryBody struct {    QueryResult *QueryResult `xml:"queryResponse>result"`}type QueryResult struct {    QueryLocator QueryLocator `xml:"queryLocator"`    Done         bool         `xml:"done"`    Size         int          `xml:"size"`    Records      interface{}  `xml:"records"`}type QueryLocator stringfunc (r *Resource) Query(sql string, r interface{}) error {     // builds xml request     // sends xml request through Resource which contains the net client     // decodes the result into r (type for records in QueryResult)}func (r *Resource) QueryMore(q QueryLocator, r interface{}) error {     // same as above except takes queryLocator and makes call to different endpoint in order to continue retrieving results, when QueryResult.Done == true, done fetching results}顯然這需要重構(gòu)，因?yàn)榭蛻舳诵枰榭词欠?Done == true 以便他們可以繼續(xù)獲取。我正在考慮添加以下內(nèi)容，并將 Query 和 QueryMore 移動(dòng)為 Querier 的一種方法：type Querier struct { r *Resource Done bool QueryLocator QueryLocator }func New(r *Resource) *查詢器{}客戶端然后會(huì)這樣表現(xiàn)：err := q.Query("sql statement", r)if err != nil {     // handle}// do stuff with rfor q.Done == false {     q.QueryMore(r)     // do stuff with r}我想知道這里的慣用方法是什么，以便最好地“流式傳輸”結(jié)果。