Account Options

  1. Sign in
Google Groups Home
« Groups Home
non-backward compatible changes for some expressions
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
John Mettraux  
View profile  
 More options Mar 25 2008, 8:35 pm
From: "John Mettraux" <jmettr...@openwfe.org>
Date: Wed, 26 Mar 2008 09:35:59 +0900
Local: Tues, Mar 25 2008 8:35 pm
Subject: non-backward compatible changes for some expressions
Hi,

I'm working on the next version of OpenWFEru, it should be very close to 1.0.

I'm currently cleaning up some process definition language
expressions. Unfortunately the changes I will make to them will render
them incompatible with previous releases' implementation.

These expressions are 'cron' (already talked about it), 'cursor',
'loop', 'iterator' and 'concurrent-iterator', as well as 'listen'.
There will be slight changes for 'when' and 'wait' but they should be
"backward-compatible".

By backward-compatibility, I'm talking about the ability to stop a pre
0.9.18 engine, replace it with a 0.9.18 or later engine and restarting
with processes ready to go.

There will three ways to migrate without [too much] pain :

1). if you don't use any of the mentioned expressions, the move should be safe
2). if you use any of them, making sure that all processes being
migrated are not inside one of those expressions at engine stop time
3). migrate manually (replay manually processes on the new server)
(4). don't migrate)

In the past, I've managed to handle such issues transparently, by
making sure that new implementations handled correctly past
implementations' rundata. But this change behind the scenes is a bit
too big this time.

The goal of these changes is to make process instance visualization
and manipulation easier. These expressions were handled in special
ways and I'm working on making their behaviour and visibility
consistent.

If you have any question, feel free to ask. I'll be glad to clarify
any detail. Best regards,

--
John Mettraux -///- http://jmettraux.openwfe.org


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »