Added my $0.02 to the wiki:
- Better user management API (server side JS module)
- Simple API to define a user/initial creation (can use own user id
scheme)
- Simple way to define different authentication backends (ex: db, web
request, LDAP, etc.)
- API to join session to existing user (easy to have same user
multiple devices/locations/browsers)
- User Rosters
- Separate channel on each user for user's roster events
- Simple Follow/Subscribe to user's roster
- Online/Offline/Timeout updates
- Ad-hoc data (e.g. updates in location, random other stuff people
want to send status updates etc)
On Thu, Jan 13, 2011 at 5:15 AM, Anthony Catel <[email protected]> wrote:
> What's the problem with user creating channels?
> At least you can disabling that feature by hooking the command on the
> server-side.
>
> Btw, I want to remove pipe, simply because it's and uncesseary abstraction
> over user/channel/... I think that new developers don't understand the
> concept.
>
> We can keep a similar concept on a lower level API.
>
> Le 12/01/2011 23:46, Damien Buhl a écrit :
>
> Hello,
>>
>> It's nice that the new APE goes in a more lightweight version, and focuses
>> itself on what he does really well. :)
>>
>> I would say don't let everyone create channels ? Set a mode where just
>> server side API can make new channels.
>>
>> I think it is really important, I've faced to this problem in the earlier
>> version.
>>
>> And I have a question why removing Pipes ?
>>
>> Kindest regards,
>>
>> daminetreg
>>
>> Trani Nicolas wrote:
>>
>>> By the way,
>>>
>>> You can find a proposal for the new client side API on this wiki page :
>>> http://www.ape-project.org/wiki/index.php/New_APE
>>>
>>> It also contain a list a of the main feature we want for APE V2. Feel
>>> free to contribute :)
>>>
>>> Regards.
>>>
>>>
>>> On 10/01/2011 07:59, Anthony Catel wrote:
>>>
>>>> Hi all,
>>>>
>>>> As some of you know, we've been working on a new version of APE (server
>>>> and client) from scratch.
>>>> (Server : https://github.com/paraboul/APE-Server-v2)
>>>>
>>>> The server code-base is almost finished and we are now ready to
>>>> implement the new APIs.
>>>>
>>>> By APIs I mean :
>>>>
>>>> - A new "RPC" protocol
>>>> - A new server C API
>>>> - A new server Javascript API
>>>> - And a new client API.
>>>>
>>>> So, it's now time to work together :) The wiki is open :
>>>>
>>>> - http://www.ape-project.org/wiki/index.php/Category:V2
>>>> - http://www.ape-project.org/wiki/index.php/Ideas
>>>>
>>>> Feel free to share your thoughts/ideas.
>>>>
>>>> Btw a new points :
>>>>
>>>> - The new server is able to stream static content (and I have some ideas
>>>> about serving dynamic content through server-side JS).
>>>> - "AJAX Push Engine" is renamed to "Async Push Engine"
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> Anthony C.
>>>>
>>>>
>>>
>>
> --
> You received this message because you are subscribed to the Google
> Groups "APE Project" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<ape-project%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/ape-project?hl=en
> ---
> APE Project (Ajax Push Engine)
> Official website : http://www.ape-project.org/
> Git Hub : http://github.com/APE-Project/
>
--
You received this message because you are subscribed to the Google
Groups "APE Project" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/ape-project?hl=en
---
APE Project (Ajax Push Engine)
Official website : http://www.ape-project.org/
Git Hub : http://github.com/APE-Project/
