[Glass] Seaside transaction management

[Johan Brichau via Glass]

Hi Dario,

Seaside in Gemstone was written by Dale to implement a transaction for each request.
If Seaside handles a request, this corresponds to a single transaction.
If the commit fails, the request will be retried after an abort.

See https://gemstonesoup.wordpress.com/2007/05/07/transparent-persistence-for-seaside/ <https://gemstonesoup.wordpress.com/2007/05/07/transparent-persistence-for-seaside/> for more info.

Does this answer what you are looking for?

best
Johan

> On 8 Jun 2017, at 12:38, Trussardi Dario Romano via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> Ciao,
> 
> 	i have seaside application.
> 
> 	I need to manage a commit after create some data (  to be commit  )
> 
> 	but before return answer to the web request.
> 
> 	The 	System commit 		in the seaside  transaction answer a error.
> 	
> 	I read  the https://github.com/GsDevKit/gsApplicationTools/blob/master/docs/gettingStarted.md#table-of-contents <https://github.com/GsDevKit/gsApplicationTools/blob/master/docs/gettingStarted.md#table-of-contents>
> 
> 	But the	 doBasicTransaction:		it's the right solutions?
> 
> 	If it is right the	 doBasicTransaction:   is sent to ? in the smalltalk code. 
> 
> 	I read the chapter 8 of : http://downloads.gemtalksystems.com/docs/GemStone64/3.1.x/GS64-ProgGuide-3.1.pdf <http://downloads.gemtalksystems.com/docs/GemStone64/3.1.x/GS64-ProgGuide-3.1.pdf>
> 	Where i can found information about transaction into  seaside applications?
> 	Thanks,
> 		Dario
> 
> 	
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20170608/9ce6aeea/attachment.html>