[interfacekit] Re: Status Updates (and more...)
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 14 Jan 2004 21:26:22 +0100
On 2004-01-14 at 01:02:43 [+0100], DarkWyrm wrote:
> >
> > On 2004-01-13 at 23:22:17 [+0100], DarkWyrm wrote:
> > > Just wondering because the list has been pretty quiet for quite
> > > some
> > > time. What's everybody up to?
> >
> > Though I'm fortunately not assigned to any task in IK context, I've
> > though
> > about implementing a little workaround for a problem with BClipboard
> > and
> > large amounts of data. Currently the clipboard data are sent through
> > ports,
> > which, due to a port message size limit, causes the clipboard to
> > cease to
> > work for data sizes of 2 MB (on R5) and more (easily reproducable
> > when
> > copying a large region in ShowImage).
> >
> > My idea to solve this problem is to pass data larger than, say, 64 KB
> > through an area (and leave it like that in the registrar). I'm
> > currently
> > stuffed with work; so, if someone else wants to implement that, I
> > wouldn't
> > mind to hand it over.
> Quite some time ago I wrote a class called AreaLink which was designed
> to make it easy to attach data to it in a way similar to PortLink but
> utilizing an area to send to another target. It's untested IIRC, but it
> might be useful for you. Use it if you like, but I won't be bothered if
> you don't, either. :)
I don't think it makes much sense in this case. BMessages are just fine for
smaller amounts of data, and for larger ones handing a whole area over to
the registrar (the application will disposses itself of it) is just perfect.
On 2004-01-14 at 01:41:36 [+0100], Axel Doerfler wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > Though I'm fortunately not assigned to any task in IK context, I've
> > though
> > about implementing a little workaround for a problem with BClipboard
> > and
> > large amounts of data. Currently the clipboard data are sent through
> > ports,
> > which, due to a port message size limit, causes the clipboard to
> > cease to
> > work for data sizes of 2 MB (on R5) and more (easily reproducable
> > when
> > copying a large region in ShowImage).
> >
> > My idea to solve this problem is to pass data larger than, say, 64 KB
> > through an area (and leave it like that in the registrar). I'm
> > currently
> > stuffed with work; so, if someone else wants to implement that, I
> > wouldn't
> > mind to hand it over.
>
> I wouldn't spend too much work on that right now, at least don't care
> about all the tiny details - I think this will be made easier in
> OpenBeOS sooner or later (because of a more advanced VM API).
It's not complicated (i.e. it should be implemented very quickly). The
available area functions are just fine for the job. Or, if you're referring
to the fact that our ports will be superior and will handle large messages
gracefully, I still don't think messaging should be used for transferring
greater amounts of data.
On 2004-01-14 at 03:19:18 [+0100], gyoder@xxxxxxxxxxx wrote:
> I mentioned this to Darkwyrm before, but in case anybody else cares I will
> mention it hear. I have been slacking off a bit on my OBOS stuff while I
> have been working on a personal project (an OS agnostic package management
> system). I expect to be getting back to the clipping and drawing code for
> the app_server soon.
> If the problem with the clipboard still exists after the new VM stuff, I
> can take care of fixing it so that Ingo can take care of more important
> stuff. I wouldn't consider that bug high priority since it isn't a very
> common case.
Fair enough. I can't promise that I won't feel like doing it till then,
though. :-P
CU, Ingo
Other related posts:
