There is no pipe "between users", a pipe is not something between users.
Simply said: Your client sends a command to the server, saying "Here is a message for this pipe". APE decides who needs to get this message. If it is a unipipe, it is sent to one user. If it is a multipipe (==channel), it decides that it needs to send this message to MULTIPLE unipipes, namely the different users (==unipipes) that joined a channel. A unipipe or multipipe is nothing but a handle you can send data to. And it's up to the APE to decide what happens next. So APE is nothing but a message distributor, absically doing a message forwarding to just one or multiple clients. The chat demo simply keeps track of all the unipipes available. When your client joins the test channel, you receive all users' nicknames and pipes and your client stores them in the background. So if you click on "Guest3" and send a message to him, you send a message to his unipipe, recalled by the client. 5 users == 5 unipipes + one multipipe for the INTERACTIVE channel==multipipe Keep in mind: There is no direct connection between the clients. All goes via the APE-Server. And you send every command to the server, telling it what to do with the data. On 30 Jul., 22:10, Tyler Slater <[email protected]> wrote: > Thanks for the help. so each user has only one unipipe? then how does the > chat/demo.js work? isn't there a pipe created between to users? so if jon > is chatting with peter and with james, aren't there separate pipes between > jon<->peter and jon<->james? so would that not be more than one unipipe for > a user? if i had 5 more users and they were all in private conversations > with each other, that would be 25 unipipes, right? > > > > > > > > On Sat, Jul 30, 2011 at 2:04 PM, Xosofox <[email protected]> wrote: > > I'm not sure your assumptions are 100% correct. > > > If I'm not mistaken, there are two types of pipes: > > > a) multipipe > > b) unipipe > > > sending something to a multipipe will make the server send this > > "something" to every user that joined this multipipe==channel. > > > And every user is/has one unipipe. Know the unipipe, send something to > > it == sending something to "a user" > > > A user does not need "a unipipe on a channel", there is just one > > unipipe per user > > > user==unipipe > > channel==multipipe > > > Und if you join a "non-interactive" channel (= a channel starting with > > *), there will be not notifications or sharing of private information > > > On 30 Jul., 11:16, Tyler Slater <[email protected]> wrote: > > > I've been learning about interactive and non-interactive channels. I > > > understand non-interactive pipes cannot be edited by users. Does that > > > mean that they cannot create unipipes on these channels? Is there a > > > way to create unipipes without all the users seeing each other? I > > > don't want all users to have access to each other's information for > > > privacy's sake. Also, it would be a lot of extra network overhead to > > > notify users who have no interest in each other. > > > -- > > 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/ -- 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/
