It is frustrating but it's actually less of a waste of resources on our 
side...
Before the timeout some people (yourself included) could hog up a few 
servers for a long time causing a heavy queue that affected all users 
regardless of rank. That means that an enterprise user would get stuck 
because you took too long to build. Usually free users didn't get to that 
point because of the jar size limit... 

After the timeout people would get stuck in a bit of a queue but once you 
timeout the queue moves and they are on their way. Even if you keep 
resubmitting you go back to the end of the line so in terms of server 
resources this is not as bad for us or for the other users. 

We obviously need to fix the underlying problem and have already done a lot 
of work to address that specifically work suggested by you. We'll look into 
the pull requests you submitted after the release and try them. This will 
allow pro/enterprise developers to use versioned build as necessary if 
something breaks.

-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/a5cf358b-4ccd-4635-b9a1-e77a44a1f24a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to