Hi Tim,

Can you give a rough estimate of when this feature will be implemented:
"Messaging layer for general messaging notifications and broadcasts with the
ElevateDB server"..?

It ain't going to be 2.03 but is it more 2.04 or, for example, 2.10..?

Thanks in advance.

Best regards,
Fons Neelen

Fons,

<< Can you give a rough estimate of when this feature will be implemented:
>>

It won't be 2.03, but most likely 2.04 around February.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> It won't be 2.03, but most likely 2.04 around February.

Thanks. That's fast enough - if it would be 2.10 then I would worry  

Best regards,
Fons

Fons


>> It won't be 2.03, but most likely 2.04 around February.
>
>Thanks. That's fast enough - if it would be 2.10 then I would worry

Worry anyway - didn't you notice no YEAR mentioned

Roy Lambert

Hi Tim,

Just wondering if there was a revised estimate on when the messaging layer might be
available?

Regards,

SteveG

Steve,

<< Just wondering if there was a revised estimate on when the messaging
layer might be  available? >>

Nothing concrete, although it will be next after 2.03 is released.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

>> Nothing concrete, although it will be next after 2.03 is released.

Ok, thanks Tim.  Looking forward to it.

Steve

Hi Tim,

I don't mean to be a PITA but just wondering if there is an updated estimate on when the messaging layer will come into being.

Regards,

Steve

Steve,

<< I don't mean to be a PITA but just wondering if there is an updated
estimate on when the messaging layer will come into being. >>

Well, there's a bit of an issue with it for 2.04, and it has been postponed
until 2.05.  I'm getting ready to do a blog post on this, but the problem is
that the current comms layer is not going to handle asynch comms without a
re-design, and I'm really not keen on having the clients poll the server for
messages.  2.04 has some other improvements that need to get out, so I'm
really not able to hold off on it much longer.

My apologies for the mess, but I've spent a lot of time analyzing this, and
it just isn't going to work in an ideal fashion with the way things are
right now.  What I'm working on doing is getting 2.04 ASAP, and then getting
to work on the comms re-design immediately thereafter.   Frankly, the
one-thread-per-connection design should go away anyways, so such a re-design
is beneficial in several ways.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim,

<< Well, there's a bit of an issue with it for 2.04, and it has been postponed
until 2.05.  I'm getting ready to do a blog post on this, but the problem is
that the current comms layer is not going to handle asynch comms without a
re-design, and I'm really not keen on having the clients poll the server for
messages.  2.04 has some other improvements that need to get out, so I'm
really not able to hold off on it much longer.

My apologies for the mess, but I've spent a lot of time analyzing this, and
it just isn't going to work in an ideal fashion with the way things are
right now.  What I'm working on doing is getting 2.04 ASAP, and then getting
to work on the comms re-design immediately thereafter.   Frankly, the
one-thread-per-connection design should go away anyways, so such a re-design
is beneficial in several ways. >>

I'm guessing it will probably be next year then?

Regards,

Steve