Compare: https://msdn.microsoft.com/pt-br/lib...v=vs.100).aspx (v4.5)
With this: https://msdn.microsoft.com/pt-br/lib...v=vs.110).aspx (v.5.2+)
Compare: https://msdn.microsoft.com/pt-br/lib...v=vs.100).aspx (v4.5)
With this: https://msdn.microsoft.com/pt-br/lib...v=vs.110).aspx (v.5.2+)
Is this Emulator compatible with RevCMS? i tried but it doesnt look compatible, idk.
Development Paused.
Since appears that the developers have abandoned the project.
Commited to Yupi
We started the Documentation of the REST API of Yupi Emulator.
What is Yupi RESTapi?
Yupi Emulator, differently that others, will not support directly Database edits, since isn't ever recommended. Yupi will be the first Post-Shuffle emulator with a defined API, used for all external communications that doesn't are made by Client <> Emulator.
The RESTapi will do stuff like SSO auth between Client and Emulator; Management of any in-game Data, RCON commands, and more.
Some Features:
1. Ability of control the server remotely
2. Ability of see the logs, hardware usage, and in-game statistics
3. Ability of control every data related to in-game things, like: {users, rooms, navigator, catalogue, furniture, groups, and more}
4. Ability of use external commands like {shutdown, restart, stats, alert}
The Item 3 will work in the following scenario:
1. The HTTP request will do something like that:
2. The REST Manager will handle it and redirect it to a desired Solution Handler (Controller), in case of Users, something like UserControlHandler.csCode:PUT https://your-server:8080/users?id=1 BODY { username : newUsername, rank : newRank, ... }
3. The Handler will do something like send a Composer to Client with the new User Data
4. NHibernate will manage and update the Data Models and execute the transactions.
5. UserControlHandler.cs will return a message to REST Manager that will deliver it back to the Requester
(Something like that.)Code:CODE: 200 OK BODY: { message : "User Edited successfully" }
You can see the RESTapi Documentation in the GitHub, in /Api/ folder. You can test the API in https://editor.swagger.io (We're using Swagger for YAML documentations)
Thanks!
- - - Updated - - -
YupiCMS
We are officially developing our CMS, made by @kylon
The CMS will have the following features:
1. Will be a small and fast CMS
2. Using Laravel or PhalconPHP as Framework
3. Composer compatible
4. Built-in Installer
5. Template Engine
6. PDO & MVC
7. REST Module
8. Communication made with Emulator totally by REST
9. Will not use Connection with DATABASE, all Data Communication, Auth and User registration will be made by REST!!
10. Using Bootstrap 3.0
11. A powerful Housekeeping were you can control all Server features, like Edit User Data, Catalogue, Furniture, User Items, Rooms, Groups, etc.
12. And more!
- - - Updated - - -
Commited to Yupi
Updated Swagger Documentation
Last edited by ovflowd; 10-10-16 at 07:16 PM.
Sorry but wouldn't it make more sense to take a microservices architecture approach like the actual Habbo?
They are currently using https://github.com/orbit/orbit/wiki for their distributed systems which looks good.
Orleans looks interesting and seems to be faster then Orbit, https://github.com/dotnet/orleans - keep up the research!
Thanks for the nice tip! @Francis Joseph. I will create now an Issue in the Repository to debate about this.
Can you explain a little bitter about what is "Orleans"?
Also what you think about the RESTapi?
Also if we're talking about scaling and redistribution we can use Cassandra for Database and Apache Hadoop.
Last edited by Taiga; 10-10-16 at 07:06 PM.
It is still supported? It's even on the main download page of the official site...
Bootstrap · The world's most popular mobile-first and responsive front-end framework.
It's nice to see a different approach for the back-end communication between web and server. This might actually be better then the socket 2 socket. Also make sure you double check your CMS info it doesn't make sense at all...
phalconphp and Laravel are two different frameworks.
Yes i know, we will use PhalconPHP or Laravel, i prefer Phalcon.
Also what you mean with |Make double check with CMS info?|
What i'm planning:
1. In CMS Settings file we have a Token (Application Token)
2. The tokens are created in the Emulator Terminal by: token-gen ApplicationName ApplicationAddress (Futurely)
3. CMS communicate with the Emulator by REST. Not by Database.
Related Issue: https://github.com/sant0ro/Yupi/issues/156
> Using Laravel (and somehow PhalconPHP)
> Calls it small
How does that even work? Lol?
Considering composer comes packaged with 90% of modern PHP frameworks, not really a valid point.
So basically this? https://github.com/RachidLaasri/LaravelInstaller
I don't really see a benefit here, you're just over-complicating it and trying to make it flashy which is completely pointless. A direct connection to the database is fine.
The use of Bootstrap is getting a bit boring now. Yes it is an excellent framework for front-end work but at least do something different. Maybe a genuine material design front-end or Semantic UI.
It means that the current text you wrote in your previous post is confusing me. You're claiming that Laravel was made by PhalconPHP. I guess it are just typos. Please consider clarifying a few things.
I'm sure you mean you do not want the users to directly interact with the database. In the post you wrote that there is no connection between the web and database. However I don't really recommend it unless you are going to use a front-end framework. Using the API will slow things a lot down it's okay if you want to use it for authentication but for the rest it's overkill. It's a nice idea but the overhead and the latency will be to much.
Correct me if I'm wrong. It's really confusing at the moment.