Re: APEX is a profile of the BEEP.
Gabe Wachob <[email protected]> Fri, 25 Oct 2002 10:27:16 -0700 (PDT)
| Newsgroups | gmane.ietf.apex |
|---|---|
| Message-ID | <[email protected]> |
There was a thread on this over a year ago. Not sure it was a question answered other than by "go ahead and try if you want". See: http://xml.resource.org/pipermail/apexwg/2001-June/000334.html -Gabe On Fri, 25 Oct 2002, Mike wrote: > Hi All, > > As mentioned in RFC 3340 in section "11. Security > Considerations" > "APEX is a profile of the BEEP.." > > Since, the Apex protocol provide a multicasted relayed > messaging service, the exact RFC just talk about BEEP > transport, though we just need a transport at beep > layer that ship one xml and get back an xml as reply. > It does not has to be beep as long as the some > transport layer provide some basic ordering and > framing service. > > Now the question is: > Does this make sense thinking of writing Apex profile > over any transport other than Beep ??? > > Regards- > Mike. > > __________________________________________________ > Do you Yahoo!? > New DSL Internet Access from SBC & Yahoo! > http://sbc.yahoo.com > _______________________________________________ > APEXwg mailing list > [email protected] > http://lists.beepcore.org/mailman/listinfo/apexwg > -- Gabe Wachob [email protected] Personal http://www.wachob.com Founder, WiredObjects http://www.wiredobjects.com