On Wed, Jan 31, 2007 at 09:52:11AM +0100, Karsten Otto wrote:
> Funny... always before, VOS basically was a system for object state
> replication. However, what you describe sounds more like a publish-
> subscribe system! I wonder whether this paradigm shift is truly
> intended? Or is the "sub
You probably already know I like this idea. For things like web
interfaces it would be awesome, in fact my web framework idea had a
design very similar to this.
best,
Lalo Martins
--
So many of our dreams at first seem impossible,
then t
Karsten Otto wrote:
> Funny... always before, VOS basically was a system for object state
> replication. However, what you describe sounds more like a publish-
> subscribe system! I wonder whether this paradigm shift is truly
> intended? Or is the "subscription" just a way of optimizing networ
Am 30.01.2007 um 20:50 schrieb Peter Amstutz:
> [...]
> c) For large updates (say over 4-8k), instead of immediately
> sending out
> new property data, the vobject sends out an invalidation message (I've
> changed, you're out of date) and the remote side has the option of
> deciding whether to g
Funny... always before, VOS basically was a system for object state
replication. However, what you describe sounds more like a publish-
subscribe system! I wonder whether this paradigm shift is truly
intended? Or is the "subscription" just a way of optimizing network
traffic?
Also, I don't
Peter Amstutz wrote:
> lightweight condition or query language that could be used for things
> like what you describe as well as searching and selecting objects for
> download.
So it would have the same syntax as site searches etc? That would be
cool as a library that could be reused. (A whi
(Forwarding this to vos-d for discussion)
On Tue, Jan 30, 2007 at 02:00:35PM -0500, Reed Hedges wrote:
>
> This new thing would be like a different kind of listener. Or an
> additional listener feature. Many listeners are monitoring the state of
> something waiting for it to be changed to a ce
