< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] FlowId Class Questions

dlb & I talked about this; if that pointer isn't in a set of valid
pointers it will be treated as bad. It really doesn't matter if we use a
map token or an existence check by a set in this case.  We definitely can't
just treat the pointer value as gospel.

Once the GruuMonkey is more written FlowId can be tweaked to work the
either way.

> -----Original Message-----
> From: Alan Hawrylyshen [mailto:alan@xxxxxxxxxx]
> Sent: Wednesday, June 08, 2005 11:48 AM
> To: Derek MacDonald; reSIProcate List
> Subject: Re: [reSIProcate] FlowId Class Questions
> On Jun 8, 2005, at 11.45, Derek MacDonald wrote:
> > I think Rohan is using them in the gruumonkey; they would go on the
> > wire in
> > a contact parameter(w/ base64encoding on to keep the size down).  The
> > serialization isn't working properly yet.
> I put forward the idea that taking a pointer from the wire is evilT.
> We had this discussion around branch parameters 2.5 yrs ago and was
> one of the main reasons (if not the only) that we decided to have a
> transaction map.
> I think these need to be a map if they are EVER interpreted based on
> user input.
> a l a n a t j a s o m i d o t c o m