Re: [WebDNA] 30 Minute Cookies
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112666
interpreted = N
texte = 249On Mar 18, 2016, at 9:10 AM, christophe.billiottet@webdna.us wrote:> What we do offer to WebDNA customers are new tools. You cannot use =[session] as you would use a [cookie]: it gives you a way to decide if =an IP change will or will not be a trigger for closing a session, it =will NOT allow a user to access his own session and represents a huge =step forward for security , it gives you the possibility to assign =sessions to robots... Your imagination and creativity is your best =friend here.>=20> About [biotype], know that several banks are showing great interest =into WebDNA based solutions and that this "small addition" might =revolutionize WebDNA future.>=20> Again, what we do here is not trying to keep an old product under =medical assistance but to create, improve and make it great again.>=20> - chris=20>=20Hi Chris,I am happy that WSC is putting resources into WebDNA improvements, and I =agree that your logic behind session could be useful. However, I agree =with Ken ( It must be a blue moon out tonight ;-) ) that it can=92t be =usedin the way you intend. I can already hear my customers being angry with =me. ;-)If I were you, I would change the name to something like [identify] (or =something more fitting). I can see a HASH like this used to make =decisions on lesser security issues, such as whether or not to ban =someone from a forum. In fact, I=92d be happy to implement that kind of =thing into my forum=85 the point is, this kind of thing needs some human =interaction associated with it=92s use. =20Regarding session=85 we already have a good one.. and yes, it does have =the option of using cookies built right in it already. I know you don=92t =like it, but it=92s a fact that it=92s one of the best features of =WebDNA which just needs a little innovation.I haven=92t read about bioType yet, but my only comment is that if it is =based off similar non-standard logic.. and if banks are indeed looking =into it, you better make sure it works. ;-) Law suites are not fun.=20New features are great, but I would lean towards creative features based =on standards. If you are to keep these tools that you created in-house, =to get us to use them, I would say that you should spell out exactly =what is going on behind the scenes.. what =93questions=94 are being =asked by the logic, etc.Just my .02=A2Sincerely,Donovan---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
.To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Associated Messages, from the most recent to the oldest:
249On Mar 18, 2016, at 9:10 AM, christophe.billiottet@webdna.us wrote:> What we do offer to WebDNA customers are new tools. You cannot use =[session] as you would use a [cookie]: it gives you a way to decide if =an IP change will or will not be a trigger for closing a session, it =will NOT allow a user to access his own session and represents a huge =step forward for security , it gives you the possibility to assign =sessions to robots... Your imagination and creativity is your best =friend here.>=20> About [biotype], know that several banks are showing great interest =into WebDNA based solutions and that this "small addition" might =revolutionize WebDNA future.>=20> Again, what we do here is not trying to keep an old product under =medical assistance but to create, improve and make it great again.>=20> - chris=20>=20Hi Chris,I am happy that WSC is putting resources into WebDNA improvements, and I =agree that your logic behind session could be useful. However, I agree =with Ken ( It must be a blue moon out tonight ;-) ) that it can=92t be =usedin the way you intend. I can already hear my customers being angry with =me. ;-)If I were you, I would change the name to something like [identify] (or =something more fitting). I can see a HASH like this used to make =decisions on lesser security issues, such as whether or not to ban =someone from a forum. In fact, I=92d be happy to implement that kind of =thing into my forum=85 the point is, this kind of thing needs some human =interaction associated with it=92s use. =20Regarding session=85 we already have a good one.. and yes, it does have =the option of using cookies built right in it already. I know you don=92t =like it, but it=92s a fact that it=92s one of the best features of =WebDNA which just needs a little innovation.I haven=92t read about bioType yet, but my only comment is that if it is =based off similar non-standard logic.. and if banks are indeed looking =into it, you better make sure it works. ;-) Law suites are not fun.=20New features are great, but I would lean towards creative features based =on standards. If you are to keep these tools that you created in-house, =to get us to use them, I would say that you should spell out exactly =what is going on behind the scenes.. what =93questions=94 are being =asked by the logic, etc.Just my .02=A2Sincerely,Donovan---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us.
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
snicker, snicker (1997)
[subtotal] and others (1997)
Attn: Scott - webdna 6.0a patch and mysql (2005)
Break out of a loop? (2000)
Access Denied! But why? (1997)
Sandboxes (2004)
WebCatalog can't find database (1997)
[movefile] create stationery files (1998)
RE: Contexts and Ampersands (1997)
Not really WebCat - need HTML Grider (1997)
using webdna to determine pixel parameters (2000)
Reloading Shopping Carts (1998)
Banners and sort of random display (1997)
WebCat2b13MacPlugin - nested [xxx] contexts (1997)
Multiple prices (1997)
Re:TARGET=window_name (1996)
Upload and WebCat (1998)
WebCatb15 Mac CGI -- [purchase] (1997)
WC TableGrinder (1997)
Customer - again (1998)