[sldev] https very slow.

[Gary Wardell]

Hi,

Well, I haven't time to look closely at the viewer, but in general, form a privacy and security standpoint (I work in these
areas), encryption is needed anytime there is personally identifiable information being passed back and forth.  Examples of this
sort of things would be names, address, credit card or bank account numbers.  Usually all three of these need to be present to
qualify.  Normally most monetary transactions need to e encrypted as they carry all of this information.

So, given that one can do monetary transaction through the viewer, it may need encryption.  However, if the transactions are
actually done on the server, and no sensitive information is in the viewer, ...

That being said, encryption would be superfluous for non-monetary transactions.

Also, it is more than a few cpu cycles.  Actually it can be significant.  It also balloons the size of the payload so it requires
more bandwidth.

Gary

> -----Original Message-----
> From: Nicholaz Beresford [mailto:nicholaz at blueflash.cc]
> Sent: Wed, July 11, 2007 12:54 PM
> To: Gary Wardell
> Cc: sldev at lists.secondlife.com
> Subject: Re: [sldev] https very slow.
>
>
>
> Btw, one of the first things I wondered about was
> the use of https in the viewer.  (Reason was of course,
> that the memory leak was caused by libcurl https
> requests.)
>
> But with the efforts of shaving cpu cycles off the
> main loop, it may be worth looking at the things that
> go through encryption, because these may eat a
> non trivial amount of cpu cycles on both ends.
>
> I have not looked at it in any depth because at this
> point I'm not interested in optimization, so I may be
> totally off the mark, but it may be worth a look.
>
>
> Nick
> ---
> Second Life from the inside out:
> http://nicholaz-beresford.blogspot.com/
>
>
>