This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Normal 0 false false false EN-AU X-NONE X-NONE MicrosoftInternetExplorer4 <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-alt:"Calisto MT"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-alt:"Frutiger 45 Light"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} span.EmailStyle15 {mso-style-type:personal; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:11.0pt; mso-bidi-font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; mso-fareast-language:EN-US;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} /* List Definitions */ @list l0 {mso-list-id:1694841221; mso-list-template-ids:-615984670;} ol {margin-bottom:0cm;} ul {margin-bottom:0cm;} -Hi Guys, I have 2 questions regarding scalability: 1. If User A uses light speed to get an object then User B uses LightSpeed to get the same object. Both user A and User B change some properties on the object. Users B then saves the object. Now when user A comes to save the object does light speed simply over write the object with the changes or throw some kind of error? 2. Is there any way that multiple instances of LightSpeed can share session on a server farm? Josh Hi Guys,
|
|
|
|
|
grrr word formatting, sorry. |
|
|
|
|
1. This depends on whether you have Optimistic Concurrency Checking turned on (or, equivalent, the LockVersion field is present). If you don't have OCC/LV, then LightSpeed does no concurrency checking, and it's last user wins: User B's version of the entity will be saved over the top of User A's. If you do have OCC/LV, then when User B tries to save, LightSpeed detects that there is a newer version in the database than the one User B has been editing, and raises an OptimisticConcurrencyException. 2. Yes, provided you only store "safe" things like IDs in session state. We advise against storing entities in session state (though it can be done, because entities are serialisable). Some things cannot be stored in session state: in particular you must NOT try to store a unit of work in session state, because a UOW encapsulates a database connection (and therefore (a) is non-serialisable and (b) has machine affinity). This means that if you do store an entity in session state, you will need to re-attach it to a new UOW when you pull it out again. |
|
|
|
