Hi guys,
I came to this post today due to having what can be described as an
unexpected voyage behavior and was greatly impressed by all the detailed
descriptions and explanations. Thanks everybody for that!
Also thanks Peter for mentioning that port I did back in the day (~2009) for
using OmniBa
Jonathan,
I was a bit destracted by work this week, so I am a little late to the
show...
Am 10.10.19 um 12:26 schrieb Jonathan van Alteren:
Hi Joachim,
Thank you for your feedback.
It feels good to know we're not alone in this :-)
Well, I guess there are far more people in this boat than
ontributed to this thread.
>
> Peter Kenny
>
>
>
> From: Pharo-users On Behalf Of Jonathan
> van Alteren
> Sent: 10 October 2019 11:39
> To: Any question about pharo is welcome
> Subject: Re: [Pharo-users] voyage mongo and transactionality
>
> Hi Peter,
>
> Th
– e.g. Bruno, who also contributed to this thread.
Peter Kenny
From: Pharo-users On Behalf Of Jonathan
van Alteren
Sent: 10 October 2019 11:39
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] voyage mongo and transactionality
Hi Peter,
Thanks for your
Hi,
That clears up some things, and I understand how the 'cache' works now, thanks!
I did a little bit of research on the lifecycle of a Seaside session, but
wasn't very successful. Largely because there is a lot of different/outdated
documentation around, including class comments in Pharo, whi
f Of
*Norbert Hartl
*Sent:* 09 October 2019 18:08
*To:* Any question about pharo is welcome
*Subject:* Re: [Pharo-users] voyage mongo and transactionality
Am 09.10.2019 um 16:48 schrieb "jtuc...@objektfabrik.de
<mailto:jtuc...@objektfabrik.de>" <mailto:jtuc...@objektfabrik.de>
> Am 10.10.2019 um 12:31 schrieb Jonathan van Alteren
> :
>
> Hah, those percentages feel very real to me at the moment :-S
>
> Can you explain what GemStone IIRC means? (Novice speaking here :-)) If
> GemStone solves this at the moment an object goes from Stone to Gem, perhaps
> we can take
Hi,
> Am 10.10.2019 um 11:48 schrieb Jonathan van Alteren
> :
>
> Hi Norbert,
>
> Thank you very much for your extensive answer.
>
> For starters, we would be happy to have an option available for the course
> grained handling that you mention. I'd be interested to hear if there are any
> o
alf Of Norbert
> Hartl
> Sent: 09 October 2019 18:08
> To: Any question about pharo is welcome
> Subject: Re: [Pharo-users] voyage mongo and transactionality
>
>
>
> Am 09.10.2019 um 16:48 schrieb "jtuc...@objektfabrik.de"
> :
> >
> > This is a
Hah, those percentages feel very real to me at the moment :-S
Can you explain what GemStone IIRC means? (Novice speaking here :-)) If
GemStone solves this at the moment an object goes from Stone to Gem, perhaps we
can take that architecture as an example and somehow apply it locally within
the
Hi Joachim,
Thank you for your feedback.
It feels good to know we're not alone in this :-) Unfortunately, the things you
describe are familiar to me. My business partner Dave West has a lot of
experience with applying a behavioral, 'pure' object design approach. We're
looking hard into simplif
Hi James,
Thank you for your feedback.
If I remember correctly, in Java a persistence framework like JPA/Hibernate
would track 'dirty' objects somehow and handle caching together with
transaction management. There might be some things we might apply from those
frameworks in Pharo/Smalltalk. Ho
Hi Estaban,
Thanks for your feedback.
I agree that there might not be any real problem with Voyage. And yes, I think
it was some kind of in-memory transaction handling that is was looking for.
Can you explain a bit more about how the cache in Voyage works and why it is
the way it is?
The appl
Hi Norbert,
Thank you very much for your extensive answer.
For starters, we would be happy to have an option available for the course
grained handling that you mention. I'd be interested to hear if there are any
options besides GemStone available to be used with Voyage/MongoDB.
Your mention of
October 2019 18:08
To: Any question about pharo is welcome
Subject: Re: [Pharo-users] voyage mongo and transactionality
Am 09.10.2019 um 16:48 schrieb "jtuc...@objektfabrik.de
<mailto:jtuc...@objektfabrik.de> " mailto:jtuc...@objektfabrik.de> >:
This is a tricky min
> Am 09.10.2019 um 16:48 schrieb "jtuc...@objektfabrik.de"
> :
>
>
> This is a tricky mine field. Sometimes you need a lot of business
> functionality in objects referenced in your objects that are currently in the
> editor. So I'm still to see a project in which the memento pattern really
Am 09.10.19 um 16:48 schrieb jtuc...@objektfabrik.de:
In my experience, this problem area makes for the other 70% of the
time spent on developing GUI or Web applications, besides the 60% for
GUI design and implementation and 25% business logic...
I forgot the 30% for O/R Mapping when you us
This is a tricky mine field. Sometimes you need a lot of business
functionality in objects referenced in your objects that are currently
in the editor. So I'm still to see a project in which the memento
pattern really worked for more complex scenarios. How deep do you dive
to have enough meme
Thanks for the explanation. And, yes, this is an artifact of your design; if
you put intermediate values into domain objects then they will remain in your
domain objects to be seen later. From what you’ve described, I don’t see how it
would be any different in a non-image environment (Java, C#,
Hi James,
I see how my explanation might be unclear.
We have a main form for the agenda and a subform for an item, which is shown
using Seaside call/answer. The save button of the subform is clicked, which
adds the item to the underlying agenda model object, but the save button of the
main for
> On Oct 8, 2019, at 3:05 AM, Jonathan van Alteren
> wrote:
>
> We've encountered an issue where a user makes changes to an agenda, but does
> not click the Save button. Instead, the user closes the browser or uses the
> navigation to go to a different part of the application. When navigatin
Hi,
> Am 08.10.2019 um 12:05 schrieb Jonathan van Alteren
> :
>
> Hello all,
>
> We are having some issues with using Voyage/Mongo for a customer project that
> I'd like to get your feedback on.
>
> The customer application is a form based business web application using
> Seaside with objec
Hi,
That looks a lot more like a Seaside mishandling than a problem with Voyage
itself.
> On 8 Oct 2019, at 12:05, Jonathan van Alteren
> wrote:
>
> Hello all,
>
> We are having some issues with using Voyage/Mongo for a customer project that
> I'd like to get your feedback on.
>
> The c
Hello all,
We are having some issues with using Voyage/Mongo for a customer project that
I'd like to get your feedback on.
The customer application is a form based business web application using Seaside
with object persistence using Voyage with MongoDB on Pharo 7.0. The application
is deployed
24 matches
Mail list logo
