Lightwave - A Scala server

[steffchef]

Hey,

It's me again!

Update 1: I removed the console from the project because I felt like it could have been better somehow, not sure whether I will redo it though (it was only a demo thing anyway).

Update 2: Started working on the shockwave server, although I'm not sure which exact version to go for yet (What do you guys prefer?). So far, I have done some of the tcp and shockwave protocol stuff (https://gitlab.com/lightwave-group/l...wave/shockwave). Nevertheless, I am planning to make the implementation more abstract, so that I can use a similar approach for flash. Just wanted to get something done (I don't fear refactoring).

Cheers,
Steve Winfield

[Bergthor]

Hey,

It's me again!

Update 1: I removed the console from the project because I felt like it could have been better somehow, not sure whether I will redo it though (it was only a demo thing anyway).

Update 2: Started working on the shockwave server, although I'm not sure which exact version to go for yet (What do you guys prefer?). So far, I have done some of the tcp and shockwave protocol stuff (https://gitlab.com/lightwave-group/l...wave/shockwave). Nevertheless, I am planning to make the implementation more abstract, so that I can use a similar approach for flash. Just wanted to get something done (I don't fear refactoring).

Cheers,
Steve Winfield

V23 is probably one of the best versions especially if done with full BB and SS.

[steffchef]

V23 is probably one of the best versions especially if done with full BB and SS.

How is it better than v26 or v35?

Cheers,

[Bergthor]

How is it better than v26 or v35?

Cheers,

Here is a visual of what I have in mind either of those version probably produce the same (maybe a few UI changes between them?)

[steffchef]

All right, I've done a more abstract front-end server approach so that I won't have to change too many things when it comes to changing the protocol.

Shockwave is a pain in the ass. There is no version for Linux available and the macOS version doesn't even work properly. That's why I had to get a virtual windows machine running (with Firefox!) in order to test it.

On top of that, I feel quite uncomfortable using the packets because I can hardly describe their structures and original names. Just take a look at this:


Well, anyway, I'll try my best!



Cheers,

[ovflowd]

@Setffchef awesome work!!!

[steffchef]

I visualized a micro-service architecture that I think could work.



Regarding the shockwave server, I introduced a message handler that routes client messages to specific handlers, so that I can eventually create multiple instances of handlers that are requested more frequently than others (FrontpageHandler > ModerationHandler, etc).



By the way I created a simple player service that handles the authentication of players as well, even though I'm not sure whether I should add a specific service that authenticates them by passwords and SSO tickets (probably not?).

Cheers,
Steve Winfield

[ovflowd]

Woah @steffchef you're really doing things in the right way.

That's really awesome. I'm wondering if you will add API Documentation, Class Documentation and also release those Software Artifacts for common public.

[steffchef]

I'm wondering if you will add API Documentation, Class Documentation and also release those Software Artifacts for common public.

What kind of documentation? I think the majority of the code is self-documenting (if you're familiar with the framework), although I'm trying to write more detailed comments from time to time.

There's already a public repository (as mentioned in the first post): https://gitlab.com/lightwave-group/l...er/tree/master

Cheers,

[Cankiee]

@steffchef check out HabboBeta - Login

[SuklaaVene]

@steffchef check out HabboBeta - Login

Its not running Lightwave, thats my own emulator called Skylight.

[steffchef]

@steffchef check out HabboBeta - Login

Might be another server that aims multi-version support.

That's not my target though, it's rather creating an out-scaling server with a microservice-like architecture. However, the feature is a great way of demonstrating the opportunities and ideas behind it.

Cheers,

[Joopie]

It might be a wrong assumption. However I prefer to say it anyway just to be sure.

Looking at your diagram and your code I get the feeling that you're creating actors based on world objects. For example, every room is a actor. At first this seems logical to do, however this wont scale. Instead actors should be made based on tasks.

Imagine having a hotel with 10 rooms. And there are 500 people spread out over the rooms. This would normally just fine, because the load is balanced. Now lets say that suddenly 400 people want to enter a single room. The other 9 rooms still works optimal, but what about that one room with 400 people more in it? Suddenly that one actor has to process allot of messages. And eventually resulting in lagg, because, as of how actors work, they process messages one by one.

The solution would be to make actors based on tasks, instead of world objects (which may be problematic as that would change your design drastically).

I'm not a pro at this, but I hope, even if my assumption is wrong, you find this usefull.
I'd like to hear your input on this thought!

[STRIKE]Let me also search a blog post about this subject I read a while ago![/STRIKE]

The blog post explaining in more depth the situation, problem and solution of this subject: Designing Akka Actor Hierarchies for Online Games - Commerce | Kotan Code　枯淡コード.

[The General]

Think you are planning to much and hoping too much that the community is going to contribute to your project which in all honesty is quite unlikely to happen.

Ofcourse I hope you will proof me wrong but I think this wont be completed or even get to a stage thats production ready.

Goodluck though.

[pel]

Think you are planning to much and hoping too much that the community is going to contribute to your project which in all honesty is quite unlikely to happen.

Ofcourse I hope you will proof me wrong but I think this wont be completed or even get to a stage thats production ready.

Goodluck though.

Like your C++ Emulator Sirius? jk jk, can agree with all of your points.