You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question, if there's any analog to http.Request.Form container planned? http.Request doc
Or any convenience methods like PeekMulti(name) (for fasthttp.RequestCtx and/or fasthttp.Request), that peek multi params both from query and body?
I guess, this may lead to increased memory usage (for http.Request.Form analog) or memory allocations (for PeekMulti(name) methods) or be tricky to implement (pooling, if possible).
Or some kind of walker method like .Visit(name, callback(value)) (also for fasthttp.RequestCtx and/or fasthttp.Request) would be also nice (and shouldn't result in memory allocs). Btw, I've read code for peekArgStr and it seems, that such .Visit method (that focuses on specific param name) would not provide any performance gain, as peekArgStr already loops through key-value pair list (and I don't think, that this should/can be optimized).
Anyway, that's just a question/suggestion; that's, obviously, not hard to work around.
The text was updated successfully, but these errors were encountered:
Both QueryArgs and PostArgs return Args, which has PeekMulti convenience method for obtaining multiple values for the same key. Args also has VisitAll method for visiting all the (key, value) pairs from Args.
Hi,
I have a question, if there's any analog to
http.Request.Form
container planned?http.Request doc
Or any convenience methods like
PeekMulti(name)
(forfasthttp.RequestCtx
and/orfasthttp.Request
), that peek multi params both from query and body?I guess, this may lead to increased memory usage (for
http.Request.Form
analog) or memory allocations (forPeekMulti(name)
methods) or be tricky to implement (pooling, if possible).Or some kind of walker method like
.Visit(name, callback(value))
(also forfasthttp.RequestCtx
and/orfasthttp.Request
) would be also nice (and shouldn't result in memory allocs). Btw, I've read code for peekArgStr and it seems, that such.Visit
method (that focuses on specific param name) would not provide any performance gain, aspeekArgStr
already loops through key-value pair list (and I don't think, that this should/can be optimized).Anyway, that's just a question/suggestion; that's, obviously, not hard to work around.
The text was updated successfully, but these errors were encountered: