Hi! >> Hello! >> A couple weeks ago we had a talk about BSession and its flaws. I >> said then that I had an idea to make it better. Now... I think I did, >Great! I was worried you would be too busy with University. University? I have a job, and it's very demanding these weeks. I am waiting a seccond reply from you, now that I've sent you the source code. >Also, never split the message into two port calls. No. I'm sorry, I will never agree with you on this one! > Then BSessionNG will know how to skip to the >next message. Please look thing the code that I've sent you. >I only had time to scribble a brief interface. I haven't seen your source but I was thinking of >one class handling SESSION and PORT_LINK, and BMESSAGE, for both reading and writing. Infact, it >would know how to mix the three protocols. PortLink and BSession can be replaced by this. BMessage was never on my "supported features list". I see no reason to add BMessage support. I must repeat myself: This is not a general purpose messaging system! This is used internaly by the Interface Kit. It covers our needs. I *do not* want to make this a BIG messaging system for everyone to use it; BMessage/BLooper system is EXCELENT! I want to keep BSessionNG at its simpliest form with all necesities that app_server team needs to have its work done. Adi. --------------------------------------------------------------- Lucram pentru tine. Analizam. Cautam zilnic. Alegem ceea ce te intereseaza. Te anuntam. http://www.REDUCERI.ro/