Confirmed users
1,136
edits
PFS2: Difference between revisions
Jump to navigation
Jump to search
→Q&A: removed batching requests
No edit summary |
(→Q&A: removed batching requests) |
||
| Line 60: | Line 60: | ||
** I think it's pretty easy to handle either case, but since we'd potentially be dealing with arrays of plugins I'd opt to accept a JSON body and have the app run logic on it. | ** I think it's pretty easy to handle either case, but since we'd potentially be dealing with arrays of plugins I'd opt to accept a JSON body and have the app run logic on it. | ||
** One argument against using POST is that doing so doesn't give you a good cache hit rate and could possibly crush the service doing operations that otherwise could be easily cached (albeit with an increase in HTTP requests). | ** One argument against using POST is that doing so doesn't give you a good cache hit rate and could possibly crush the service doing operations that otherwise could be easily cached (albeit with an increase in HTTP requests). | ||
* Will there be a batch request mode, or 1 request per plugin? | * Will there be a batch request mode, or 1 request per plugin? | ||
** Leaning towards 1 request per plugin at this point, but we should take some time to figure out which solution is best. | ** Leaning towards 1 request per plugin at this point, but we should take some time to figure out which solution is best. | ||