Why is it junk? The product, implementation, or this transient front end http sprayer configuration fuckup? (larger web companies had more spectacular fuckups :-)
By the way, they use Grails for a small side product, not the main site. Even there its just as UI layer not for business logic.
Message like that shouldn't be ever presented to the user. Say "service temporarily unavailable", but don't give out details on your internal architecture, and certainly not on your maximum number of connections. This can be easily exploited by hackers, which certainly doesn't please users who entrust personal information with this server.
3 comments:
Grails to be exact!
Best.
alain
Why is it junk? The product, implementation, or this transient front end http sprayer configuration fuckup? (larger web companies had more spectacular fuckups :-)
By the way, they use Grails for a small side product, not the main site. Even there its just as UI layer not for business logic.
Message like that shouldn't be ever presented to the user. Say "service temporarily unavailable", but don't give out details on your internal architecture, and certainly not on your maximum number of connections. This can be easily exploited by hackers, which certainly doesn't please users who entrust personal information with this server.
Post a Comment