Re: [sc-users] commit: Revised Buffer (possible solution)

[Scott Wilson <sdwilson@xxxxxxxxxxxx>]

Okay, I've committed this. So it should now work even if the server is not running.

S.
On 14 Dec 2004, at 01:07, Scott Wilson wrote:

> Thinking about this more, I think these are probably a good idea, and would be consistent with the way the allocators work. I'm probably being too fussy worrying about it not throwing an error, as it's probably self-evident that you'll have problems if the server isn't running.
>
> If nobody objects I'll commit both of these.
>
> S.
>
> On 13 Dec 2004, at 13:29, Scott Wilson wrote:
>
> > That said, I can see a potential two-pronged solution to both your and Jan's problems:
> >
> > 1. Change Buffer so that the array gets created in Server-init, and everytime it boots or quits. This means that things will be out of sync if you create stuff while the server isn't running, but this is in fact the way that the allocators work currently, so I suppose that's not any worse than the way other server abstractions function in this situation. In some ways I feel this is a little like leaving banana peels on the sidewalk for people to trip on, so I have mixed feelings, but this would solve your 'debugging' problem.
> >
> > 2. Change Buffer-new so that it doesn't call addToServerArray, and do it instead in the instance methods alloc and allocRead, and probably the corresponding Msg methods as well. I think this may solve Jan's problem, if I understand the way he's working.
> >
> > Thoughts?
> >
> > S._______________________________________________
> > sc-users mailing list
> > sc-users@xxxxxxxxxxxxxxx
> > http://www.create.ucsb.edu/mailman/listinfo/sc-users
> _______________________________________________
> sc-users mailing list
> sc-users@xxxxxxxxxxxxxxx
> http://www.create.ucsb.edu/mailman/listinfo/sc-users