bulk request for url resolve

[sebschlicht]

do we need a bulk request for url resolving or do we work async in middleware

[renepickhardt]

maybe for muid resolving. There are pro's and con's in a discussion with @lukasschmelzeisen we have decided to make everything async in the beginning.

@JonasKunze what do you think?

[JonasKunze]

Why does github tell me today that I have unread notifications?

Anyway, I'd say that I would prefer having a bulk import soon as this should massively reduce the network load. What do you assume how many MUIDs you'll typically have within such a request? I have the feeling that having more than 10 MUIDs within a request it's really worth having a bulk import and I guess we'll typically have O(100) MUIDs in each request....
If it's really so much work, let's postpone it and stay async until we've done some performance tests...

[sebschlicht]

Although I have not looked in the code for several months now, I think it's not much work. We have to change the response class to hold a list of resolved MUID rather than a single instance and put a loop in the high level method "resolveMuid" or something like that. Asking the question was easier than doing that, I guess. I honestly doubt that now, but "keep it simple" 4tw.