quasarchimaere

i move this to clarify, so we can talk about finding a solution where our distributed system is actually handling loss/regain of connections between the components without having to restart...

moved this to soon, it does not make sense to alter the documentation until further notice

We could define a set of probable details based on the type of needs that are connected to eachother over the given facet, however its probably easier to just define...

clarify because approach to use needs further specification

@sigpie this might be true if we choose a library which we can't "extend" or "adapt" from, i think for certain cases it might still be ok to create unique...

link doesn't lead anywhere any more here is the a new one: https://www.baeldung.com/spring-security-csrf

although this happens mostly on file or image upload the underlying problem seems to be the websocket message size limitation (afaik)

scaling would only work for images but not for general file upload. we need to figure out a way to handle bigger details/ long content with a different approach, sending...

@maxstolze i think it is just a general issue, that we do not implement or handle any creation errors, and do not allow resubmitting when an attempt has failed due...

I think this would be an "epic"-issue, What should be done first is: - Implement a way to parse need-content (e.g. details) serverSide - Implement a way to parse message-content...