RIFE 1.5 Milestone 2 has been released (this time with an email
subject ;-) )
The web engine's internals have been heavily refactored and
optimized, which is why this is still a milestone release and not a
final one.
You get a speed release during development with this release,
compared
RIFE 1.5 Milestone 2 has been released.
The web engine's internals have been heavily refactored and
optimized, which is why this is still a milestone release and not a
final one.
You get a speed release during development with this release,
compared to version 1.4. Before, RIFE checked for
> I'd like to take a look at RIFE-270.
Does this change imply that element.dtd would be changed, to add
"submit" as a subelement of the "submission" element? And the
SiteBuilder API updated accordingly?
Just checking..
Actually I realize I probably have it backwards, it's the API that
is updated
Ok ... was just starting a mail to explain it :-)
On 09 Jun 2006, at 16:22, Eddy Young wrote:
Eddy Young wrote:
Geert Bevin wrote:
Hi everyone,
I went over the issues in the issuetracker (http://uwyn.com/
issues/browse/RIFE) and thought it might be a good idea to
provide a list of issues
Eddy Young wrote:
Geert Bevin wrote:
Hi everyone,
I went over the issues in the issuetracker
(http://uwyn.com/issues/browse/RIFE) and thought it might be a good
idea to provide a list of issues that seem doable for someone that
wants to start contributing to RIFE without knowing much about a
Geert Bevin wrote:
Hi everyone,
I went over the issues in the issuetracker
(http://uwyn.com/issues/browse/RIFE) and thought it might be a good idea
to provide a list of issues that seem doable for someone that wants to
start contributing to RIFE without knowing much about all the internals
o
> Hmmm, you're mostly right, except for Wicket where there really is no
> overhead it seems. They just instantiate a new component. No
> configuration is needed for that, so there are less steps and less
> files. My problem with that is that it might seem nice in small
> example application
Hi everyone,
I went over the issues in the issuetracker (http://uwyn.com/issues/
browse/RIFE) and thought it might be a good idea to provide a list of
issues that seem doable for someone that wants to start contributing
to RIFE without knowing much about all the internals or their
relation
Hi Stefan,
RIFE hasn't got direct support for this in the web engine, but you
can retrieve the used domain name through getServerName(). I remember
that somewhere in the past there were some discussions about adding
support for domain name mapping in a similar fashion as the current
pathi
Well, other frameworks have solutions for that too. In Wicket you
just create a new instance of a component, in Spring Web Flow you
return any object from your execution method and redirect the flow
based on an introspection of that, in WebWork you return a result
identifier that you tied to a nex
Hi Geert,
Where do you find the time? Thanks a lot again.
I do not remember why I left this try/catch block in there and of course
you right that it is not a good practice this way (Probably because not
all persons in the database are travellers and therefor are tied to a
seat, some are only c
11 matches
Mail list logo
