1

当用户点击路由时,我会发出 NATS 请求,然后等待回复:

ctx := r.Context()
reply, err := natsConnection.RequestWithContext(ctx, "Subject", payload)

订阅者将执行一项资源密集型任务:

natsConnection.Subscribe("Subject", func(m *nats.Msg) {
    //do consuming task and cancel if the request was cancelled. 
    natsConnection.Publish(m.Reply, []byte("Reply"))
})

如果请求被取消,我如何告诉订阅者停止工作。

context我想为工作人员收到的每条消息创建一个,然后给发件人一个新inbox的等待回复,或者向它发送一个取消通知:

contextMap := map[string]func(){}
natsConnection.Subscribe("Subject", func(m *nats.Msg) {
    ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)

    //create new inbox
    inbox := nats.NewInbox()

    //subscribe to the new inbox and cancel and clean up the current task is something is recived
    newSub, err := natsConnection.Subscribe(inbox, func(m *nats.Msg) {
        contextMap[inbox]()
    })

    contextMap[inbox] = func() {
        fmt.Println("recived")
        cancel()
        delete(contextMap, inbox)
        newSub.Unsubscribe()
    }

    //tell the requester to wait for reply in this inbox
    natsConnection.Publish(m.Reply, []byte(inbox))

    //do the work and send the reply when finished
    tick(ctx)
    natsConnection.Publish(inbox, []byte("done"))
})

在请求者端,我发送第一个请求并在指定的时间内等待inbox回复或被context取消,在这种情况下,我会向接收者发送一条消息inbox

ctx := r.Context()
inbox, _ := natsConnection.RequestWithContext(ctx, "Subject", []byte("Payload"))

reply := make(chan *nats.Msg, 1)
natsConnection.ChanSubscribe(string(inbox.Data), reply)

select {
case <-ctx.Done():
    fmt.Println("Canceled")
    natsConnection.Publish(string(inbox.Data), []byte(""))
    return
case r := <-reply:
    fmt.Println(string(r.Data))
}

tick只是一个打勾的功能:

func tick(ctx context.Context) {
    ticker := time.NewTicker(time.Millisecond * 500)
    for {
        select {
        case <-ctx.Done():
            ticker.Stop()
            fmt.Println("context was canceled", ctx.Err())
            return
        case <-ticker.C:
            fmt.Println("Tick")
        }
    }
}

现在这可行,但我想知道是否有更简单的方法可以做到这一点,或者如果没有,我怎样才能使这段代码更好?

4

2 回答 2

1

If the response is intensive and takes multiple seconds to produce, then yes you can send a separate message that kills the request. Most architectures however let the responder continue and throw away the result.

于 2018-07-01T20:21:37.470 回答
0

What are you trying to save from cancelling the request? The work on the request or the transmission of a reply that you know will not be used?

于 2018-06-30T21:56:49.097 回答