Hi,
I have a custom login which is plugged in the zone.
Do i need to plug my room code in the room or can all go through the zone extension.
in other words, one jar that has all the logic or split up the zone extension and room.
Are there advantages/disadvantages ?
Thanks,
Eddy.
Zone/room extension
I am going to skip over the use of annotations and just give my 2 cents in the broad case.
Handling everything through a zone extension has the advantage of less object creation. It requires more state handling for rooms via the room variables. It may get tricky deciding to which room the client may be sending a request.
Splitting into zone and room extension has the advantage that there is an extension object created for each room and therefore has its own state. The client is required to specify a room in the request. There could be significantly more objects created in the server.
I am using one jar in an extension subdirectory. It contains the room extension class and zone extension class, as well as all handler classes. It's just a matter of specifying the appropriate class during room/zone creation.
Handling everything through a zone extension has the advantage of less object creation. It requires more state handling for rooms via the room variables. It may get tricky deciding to which room the client may be sending a request.
Splitting into zone and room extension has the advantage that there is an extension object created for each room and therefore has its own state. The client is required to specify a room in the request. There could be significantly more objects created in the server.
I am using one jar in an extension subdirectory. It contains the room extension class and zone extension class, as well as all handler classes. It's just a matter of specifying the appropriate class during room/zone creation.
Who is online
Users browsing this forum: No registered users and 128 guests