In my current configuration with regards to the wave federation protocol (not the wave sandbox) I have the wave protocol client/server running on a low power server that's up 24/7 and then to add waves and manage the server I use SSH on my main desktop. Therefore from a client standpoint I don't have to open up any ports to my desktop or change any of the IDS settings. In fact, all I need is a SSH client and a connection to the server which has both the wave client/server and ssh server running on it.
On Aug 29, 6:25 am, James Purser <[email protected]> wrote: > Phil Wayne wrote: > > Typically IP packets ~64 bytes raise an alarm and typically indicate > > virus activity on a sub network. > > > Character by character transmission is great and no impact on IDS even > > better. > > > As I understand it, wave is based on P2P architecture and I would > > suggest growth out there might be impacted in the event IDS or other > > equivalent systems are rendered useless. > > Where do you get the impression that wave is based on p2p? It's very > much a server/client technology and as far as I know relies on no p2p > foo. In fact I'd go so far as to say that it's about as p2p as email. > > -- > James Purser > Collaborynthhttp://collaborynth.com.au > Mob: +61 406 576 553 > Skype: purserj1977 > twitter:www.twitter.com/purserj > GTalk: [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
