[interfacekit] Re: BSession
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 14 Apr 2004 13:55:12 +0200 CEST
Pahtz <pahtz@xxxxxxxxxxxx> wrote:
> The "int32 code" parameter is NOT the BMessage's "what". Developers
> may use it as they wish, but within the appserver and IK, it
> represents
> the message protocol, so we should write "int32 protocol".
Where should we write this?
The port mechanism is a system wide kernel based IPC service.
[...]
> AS_SERVER_SESSION
[...]
> This is where I get suspicious.
[...]
> Also BSession had all the return error codes removed. I'm unable to
> create
> robust software with it.
That's another thing I mentioned when it happened, but it obviously
didn't get repaired.
To sum it up: that thing is serverly broken and very inefficient in a
lot of ways.
I am not sure if the AS_SERVER_SESSION is going to be used in the
future, but if that's the plan, I would think again about it, or
rewrite it.
Adi, DarkWyrm, what's the word on this one?
Bye,
Axel.
- References:
- [interfacekit] BSession
- From: Pahtz
Other related posts:
- » [interfacekit] BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- » [interfacekit] Re: BSession
- [interfacekit] BSession
- From: Pahtz