Hi
I will slowly compile a list of features/changes/fixes for the next version API.
What would you like to see?
I already got a little list myself, and will post that later to this thread. Want to hear what _you_ think first.
Best
Thomas
Request for 1.2 features/changes
-
- Posts: 1297
- Joined: 14 Mar 2008, 07:52
- Location: Sweden
- thecreatrix
- Posts: 19
- Joined: 20 Aug 2008, 02:32
- Contact:
-
- Posts: 1297
- Joined: 14 Mar 2008, 07:52
- Location: Sweden
Should be "soon" as in "around GDC" which is next week
Previews only available for beta list members
Anyways - not much feedback from people. Means either no one is reading/using - or no one has any suggestions and are happy.
So here is my compiled list of _candidates_
* non-static SFSEvent
* refactor the room creation to be object based instead of hashtables
* code re-organization/cleanup and adding #regions for easier navigating the sources
* stronger validations in general of input data
* a look at proxies - http, https, socks5
* support for Unity iPhone Advanced (and maybe Basic through WWW class)
If you feel strongly for some of those - or have additional ones, then reply here with your comments. Else I will decide (with input from Marco too)
/Thomas
Previews only available for beta list members
Anyways - not much feedback from people. Means either no one is reading/using - or no one has any suggestions and are happy.
So here is my compiled list of _candidates_
* non-static SFSEvent
* refactor the room creation to be object based instead of hashtables
* code re-organization/cleanup and adding #regions for easier navigating the sources
* stronger validations in general of input data
* a look at proxies - http, https, socks5
* support for Unity iPhone Advanced (and maybe Basic through WWW class)
If you feel strongly for some of those - or have additional ones, then reply here with your comments. Else I will decide (with input from Marco too)
/Thomas
I'm just getting started with SFS and Unity3D, but from what I've read here about the new message queueing feature added in 1.1, I would like to see more control from the game side of processing the messages in the queue.
For example, when I would like to be able to find out how many messages are in the queue and more importantly be able to have a call that only processed a single message in the queue instead of all of the messages in the queue. That way the game can choose how many of the network messages it wants to process during any particular frame or FixedUpdate handler.
Thanks!
David
For example, when I would like to be able to find out how many messages are in the queue and more importantly be able to have a call that only processed a single message in the queue instead of all of the messages in the queue. That way the game can choose how many of the network messages it wants to process during any particular frame or FixedUpdate handler.
Thanks!
David
-
- Posts: 1297
- Joined: 14 Mar 2008, 07:52
- Location: Sweden
-
- Posts: 1297
- Joined: 14 Mar 2008, 07:52
- Location: Sweden
OK - started work on 1.2 today. So if you have anything beyond the already stated, then its time to come forward!
Not everything will get into this version (from the list of potential features).
Right now I have reorganized the code, fixed a few bugs / improved validation at room creation, added some extra methods to the queue mode API and right now working on the "object based" room creation.
The litjson library is now also ported over to be included in the build instead of using the dll - this is for preparation for running on the iPhone, as that doesnt allow for dll plugins yet.
So who knows what else will get in there
Ohhhh! Before I forget. There are some changes here that will need good testing. Anyone using json for communication protocol that wants to beta test a bit?
/Thomas
Not everything will get into this version (from the list of potential features).
Right now I have reorganized the code, fixed a few bugs / improved validation at room creation, added some extra methods to the queue mode API and right now working on the "object based" room creation.
The litjson library is now also ported over to be included in the build instead of using the dll - this is for preparation for running on the iPhone, as that doesnt allow for dll plugins yet.
So who knows what else will get in there
Ohhhh! Before I forget. There are some changes here that will need good testing. Anyone using json for communication protocol that wants to beta test a bit?
/Thomas
Return to “.Net / Unity3D API”
Who is online
Users browsing this forum: No registered users and 11 guests