Is it a good practice to combine different parameters in to a single entity part in a MultiPart call?

Question

In our project we are using the Multpart (http.entity.mime.MultipartEntity) to send data to the backend. Now, we have a new requirement which basically states the need to restrict the number of parts to two in a MultiPart request.

Normally, we added a new part for each parameter:

entity.addPart("parameterName1",new StringBody(parameterValue1));
entity.addPart("parameterName2",new StringBody(parameterValue2));
entity.addPart("parameterName3",new StringBody(parameterValue3));
entity.addPart("parameterName4",new StringBody(parameterValue4));

Now the requirement is like:

entity.addPart("parameterName1",new StringBody(parameterValue1+"|"+parameterValue2+"|"+parameterValue3));
entity.addPart("parameterName2",new StringBody(parameterValue2));

I would like to know if this is a good standard to follow and will this always restrict the number of parts to "two" in the Multipart call?

score 1 · Accepted Answer · answered Jun 12 '12 at 21:18

1

I would not say restricting multipart request to only two or any specified number as best practice but you can do that, make sure that is not an practice, you might want to explore business case more to get clear understanding of the requirement.

answered Jun 12 '12 at 21:18

Rachel

100,387
116
269
365

Is it a good practice to combine different parameters in to a single entity part in a MultiPart call?

1 Answers1