[ python-Bugs-1002784 ] Lazy Proboscis

[noreply at pgfoundry.org]

Bugs item #1002784, was opened at 2007-04-01 11:37
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1002784&group_id=1000094

Category: FE/Proboscis
Group: To do
Status: Open
Resolution: None
Priority: 4
Submitted By: James Pye (jwp)
Assigned to: James Pye (jwp)
Summary: Lazy Proboscis

Initial Comment:
Currently, just about every database action requires the client to wait for the response. This isn't always necessary from a client's standpoint. Rather, it's only necessary to get the response when the response is requested.

For instance, in the usual Prepare->Bind->Execute scenario, it is only until execution occurs that the user wants to see information. So why require the user  to suffer the cost of the latency involved in three round trips when only one is necessary?

The only time this is really desired is when the user wants to realize success for a given segment, so an interface allowing realization is necessary.

Currently, I think it best to make lazy mode the default.

----------------------------------------------------------------------

>Comment By: James Pye (jwp)
Date: 2007-12-11 23:54

Message:
The version of Proboscis in the works creates an idea of "stepping" through a protocol transaction. This will give the implementation the ability to prime transactions so that when the user comes back to an object, it's already been prepared or bound, or whatnot. However, this is not lazy evaluation.

----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=442&aid=1002784&group_id=1000094