[interfacekit] Re: PortLink(NG)

Greetings!

--- Adi Oanca <adioanca@xxxxxxxxx> wrote:
> 
> Hello!
> 
> Pahtz wrote:
> > I have made all the changes to the interface kit (on my local HDD) to use 
> > the new PortLink.
> > 
> > The majority of the changes are going to be necessary even if we don't 
> > merge BSession and
> PortLink
> > since the CVS BSession needed to change anyway.
>       If we are going to to something good, BSession and PortLink need to 
> disappear.

Sure, I named it PortLink but you can change it.

>       I will have a look on Sunday at your PortLinkNG code. *I will agree to 
> use it if the majority on this list approves that the buffer 
> allocation/deallocation scheme you are using is good enough to be used 
> by app_server*.

It can be easily modified for fixed size static, fixed size malloc'd, resizable 
malloc'd.

>       I will have some questions for you, but you will see them on Sunday. 
> Meanwhile this is want I don't like about your code:
> * Code does not need to be compatible with PortLink/BSession. It has to 
> be what we need.

Partly I converted all of IK so make sure it is suitable for how it needs to be 
used.
I will analyse app_server further.

> * your send/rcv buffer keeps increasing... you may need a method to 
> shrink it, otherwise it will use more that it needs. Ex: send a big BRegion.

I just need a decision algorithm or some default/max sizes to be decided.

> * with your buffer growing more and more, you can accommodate more and 
> more BWindow/BView messages, which is bad because the user should see 
> results of his drawing/actions on screen. A limit must be set to 
> automatically flush the send buffer when it reaches a certain size.

Yes, but also our developers will call Flush() when they know it's a good place 
to do so. Either
way is fine until we gather some runtime stats to support one over the other 
(or both).

> 
> > There are again a bunch of changes for the appserver. I would not wish it 
> > on DW, so I will do
> it.
>       :-| But we didn't agreed with your changes! And we don't need help in 
> that area. If you are willing to do something for the app_server I think 
> you should first ask, not pump in and do what you think is good. 

No worries, I am just talking about PortLink changes.

Great to hear app_server is going well. Don't worry, I don't want to do 
app_server internals. I'm
concerned with IK, but it's closely related to app_server.

Latest versions will be here (PortLink.cpp is still being tweaked.

http://home.swiftdsl.com.au/~pcky/beos/PortLink.h.txt
http://home.swiftdsl.com.au/~pcky/beos/AppServerLink.h.txt
http://home.swiftdsl.com.au/~pcky/beos/AppServerLink.cpp.txt

Cheers,
Paul.

> app_server is progressing well, even if in the last month neither I, 
> Gabe or DW had done consistent changes. Still, I have quite some changes 
> to commit, which will make windows move and resize properly. Soon, in a 
> week or two (3 if I'm rally busy at work) I will start making 
> BWindow/BView assembly fully work with the server.
>       app_server has come a long way, and now that I will be more free and DW 
> coming back by the time of WalterCon, thing will be back on track and 
> big results won't take long to appear.
> 
> > Now all I need is the green-light to go ahead with it. It's a bottle neck 
> > and we all want to
> get
> > on with making the appserver do something we can take a screenshot of don't 
> > we?
>       Ha ha haaa! Screenshots of the Application Server were taken since the 
> time of prototypes. Our team already has 4 members, and I don't think 
> that you can do much because everyone of us has its part assigned, and 
> sincerely there aren't any parts left. Still, suggestions are welcomed.
>       If you want to help, check the Kernel Team. I know they are looking for 
> talented people.
> 
> 
> 
> Adi.




        
                
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover

Other related posts: