This week's book giveaway is in the Cloud/Virtualization forum.
We're giving away four copies of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds and have James Denton on-line!
See this thread for details.
Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

standalone mode and threadsafe, Doubt?  RSS feed

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The SCJD2 assignment states:


Non-Networked Mode
In this mode, the database and User Interface must run in the same VM and must perform no networking, must not use loopback networking, and must not involve the serialization of any objects when communicating between the User Interface and database elements.


My doubt is:
If non-networked ( or standalone) mode and server mode run in the same machine, at the same time.
Do they need 2 database files?
If not, how to achieve thread safe?
if yes, how to achieve data integrity?
Thanks for any help!
Leif
 
Sheriff
Posts: 12318
200
Android Debian Eclipse IDE IntelliJ IDE Java Linux Mac Spring Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Leif,
Don't try to read too much into the
requirements. Keep things simple and stick with what is explicitly asked for. As long as you can run in either mode, you don't need to worry about running in both modes at the same time if this is not explicitly stated in the requirements.
If you feel you really need to say something about the situation you have in mind, you might want to document it in your design choices documentation as an issue that you are aware of.
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!