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
Will a HEAD method be necessary? HEAD is extremely useful in a very particular scenario in HTTP APIs, that is whenever a client wishes to know the metadata of a big payload without actually downloading the payload.
While it is conceivable that JSTP applications may wish to generate a "demo" "response" from a remote Engine, there are two reasons not to simply implement HEAD:
There is no such thing as a response in JSTP, that's why the quotes. A HEAD seems to me to make little sense in the context of JSTP broadcasting.
It has still to be proven useful in an actual JSTP usage.
Will leave this here for now.
The text was updated successfully, but these errors were encountered:
Will a HEAD method be necessary? HEAD is extremely useful in a very particular scenario in HTTP APIs, that is whenever a client wishes to know the metadata of a big payload without actually downloading the payload.
While it is conceivable that JSTP applications may wish to generate a "demo" "response" from a remote Engine, there are two reasons not to simply implement HEAD:
Will leave this here for now.
The text was updated successfully, but these errors were encountered: