no not yet Carl

the bug needs to be fixed too, jvm Target should stay at 1.6

@jchildress Good to know, if others run into this error we know what to look for now.

It's not really your fault 🙂 It was my dependencies... just had to check....

@carlw I'm with @ron I thought were were still on 1.6

does 1.8 work too?

i was running 1.8 without a problem yesterday

k

good to know...

but I don't think i was using the default parameter construct that was mentioned on the slack

🍰 🎂 🌞 another big part added to keepassFX, thanks to tunnelij I reversed engineered another part of the protocol and got it working 🙂

I am so happy now

if you ever need a simple http sniffer, look at the tunnelij plugin for intellij

only one more to crack

hopefully "crack" is just a pun when it comes to keypassfx

it is, the protocol is a bit weird

oh do you mind reviewing some code?

I complete rewrote the server handling to kotlin in the last few days and there are some parts I am not too happy about

@User uploaded a file: serverCommands.kt

will singleton scale with HttpServlet? The last time i did something like that i had to use single threaded model

in this case it does

this is actually the standard way of doing it with guice and jetty

brb

@ron the code looks fine to me. i read the article about -at-Singleton being required for Guice. Do you think that decoder might be a problem? Could Jetty hand out two references to the Singleton to 2 threads and cause decoder corruption?

You can run your own code against 1.8 for sure, but TornadoFX has some functions with default parameters that causes the compiler to generate faulty byte code.

@ron I haven't used Kotlin on the server-side before. I'd like to see a RESTful implementation that can parse out the JSON and handle form parameters automatically.

@carlw https://github.com/google/guice/wiki/ServletModule

time for bed here, thanks for looking at the code @carlw I have some ideas to clean it up a bit, this is very much a “first make it work, then make it pretty” kind of code

words i'm living right now. in fact, i'd shoot for make it work, make it not unbearably ugly the only improvement i'd suggest is a framework for handling the parameters which replaces the HttpServletRequest or JSONBody args with something domain-y. That might mess up what you have going w. Jetty and Guice though. With the decoder, you're checking to make sure that Jetty blocks if one user is logging in while the other is doing an association so that their use of decoder is controlled.