Hello, I've yet to really understand which decisions for my Page and Component classes regarding member variables lead to what amount of increase in memory usage or bandwidth usage. Are there any documentation pages that I've maybe overlooked?
For example, I have a page and database entities used in the page. What is the difference in using @Persist for these entities? If I don't use @Persist, are these objects only stored server-side in the VM? If I use @Persist, - where is the data stored on the client side? In a cookie? Could I read this data? - What does using SESSION lead to? Creating a session cookie? - should I rather persist primitive type (e.g. int) entity ID's in the page or can I use the entities themselves? - Does JPA.ENTITY automatically store only the entity ID's in the cookie between requests? Should I rather use entity ID's or entities? If entities are used in multiple methods, they always needed to loaded via DAO. After the first query the objects probably are cached to speed up later ones, aren't they? Regards, Daniel Poggenpohl -- Dipl. Inf. Daniel Poggenpohl, Fraunhofer-Institut für Software- und Systemtechnik ISST Compliance- und Sicherheitslösungen Emil-Figge-Straße 91, 44227 Dortmund, Germany Telefon: +49 (0) 231 / 9 76 77-323 mailto: daniel.poggenp...@isst.fraunhofer.de<mailto:daniel.poggenp...@isst.fraunhofer.de> http://www.isst.fraunhofer.de<http://www.isst.fraunhofer.de/>
