Thread

aw_contact_... (Sdk)

aw_contact_... // Sdk

1  |  

=?iso-8859-1?q?=c6dificator?=

Feb 10, 1999, 3:19am
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Roland, if you will...
<p>What is/will be the status on the contact list capability (aw_contact_stuff)?&nbsp;
I haven't noticed any talk about it.&nbsp; I'm making a tour guide, and
it would be really nice to have it inform me of visitors while I am away,
much less the other stuff I can do with it...&nbsp; Seeing it in the API
reference is like yummy candy in a locked glass case! heh heh
<p>- &AElig;dificator</html>

roland vilett

Feb 10, 1999, 3:50am
This is a multi-part message in MIME format.

------=_NextPart_000_000B_01BE5476.2B20DA40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Unfortunately, supporting contact lists from SDK apps will require some =
significant re-write of the contact handling code in the uniserver. =
Currently the mechanism depends on the owner of a contact list having a =
unique citizen number, so that will have to be changed first.

Hopefully, we'll get this into a future version of AW...

-Roland
[View Quote] - =C6dificator=20


------=_NextPart_000_000B_01BE5476.2B20DA40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!doctype html public "-//w3c//dtd html 4.0 =
transitional//en">
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>Unfortunately, supporting contact =
lists from SDK=20
apps will require some significant re-write of the contact handling code =
in the=20
uniserver.&nbsp; Currently the mechanism depends on the owner of a =
contact list=20
having a unique citizen number, so that will have to be changed=20
first.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Hopefully, we'll get this into a future version of=20
AW...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Roland</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>&AElig;dificator<AEDIFICATOR~NOSPAM! at GEOCITIES.COM> wrote in =
message=20
&lt;<A=20
=
href=3D"mailto:36C116C8.3E00893A at geocities.com">36C116C8.3E00893A at geociti=
es.com</A>&gt;...</DIV>Roland,=20
if you will...=20
<P>What is/will be the status on the contact list capability=20
(aw_contact_stuff)?&nbsp; I haven't noticed any talk about it.&nbsp; =
I'm=20
making a tour guide, and it would be really nice to have it inform =
me of=20
visitors while I am away, much less the other stuff I can do with=20
it...&nbsp; Seeing it in the API reference is like yummy candy in a =
locked=20
glass case! heh heh=20
<P>- &AElig;dificator </P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000B_01BE5476.2B20DA40--

walter knupe

Feb 10, 1999, 3:38pm
This is a multi-part message in MIME format.

------=_NextPart_000_009C_01BE5524.82AFDE60
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Does that apply to the file sending stuff which is defined in aw.h as =
well ?

Walter aka Faber

Roland Vilett schrieb in Nachricht <36c11d81.1 at homer>...
Unfortunately, supporting contact lists from SDK apps will require =
some significant re-write of the contact handling code in the uniserver. =
Currently the mechanism depends on the owner of a contact list having a =
unique citizen number, so that will have to be changed first.
=20
Hopefully, we'll get this into a future version of AW...
=20
-Roland
[View Quote] - =C6dificator=20


------=_NextPart_000_009C_01BE5524.82AFDE60
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<META content=3D'"MSHTML 4.72.3511.1300"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000080><STRONG>Does that =
apply to the=20
file sending stuff which is defined in aw.h as well ?</FONT></FONT><FONT =

color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2><FONT =
color=3D#000080><STRONG></FONT></FONT><FONT=20
color=3D#000080></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#000080><STRONG>Walter =
aka=20
Faber</FONT></FONT><FONT color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>Roland Vilett<ROLAND at ACTIVEWORLDS.COM> schrieb in Nachricht=20
&lt;36c11d81.1 at homer&gt;...</DIV>
<DIV><FONT color=3D#000000 size=3D2>Unfortunately, supporting =
contact lists from=20
SDK apps will require some significant re-write of the contact =
handling code=20
in the uniserver.&nbsp; Currently the mechanism depends on the owner =
of a=20
contact list having a unique citizen number, so that will have to be =
changed=20
first.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Hopefully, we'll get this into a future version =
of=20
AW...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Roland</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
<DIV>&AElig;dificator<AEDIFICATOR~NOSPAM! at GEOCITIES.COM> wrote =
in=20
message &lt;<A=20
=
href=3D"mailto:36C116C8.3E00893A at geocities.com">36C116C8.3E00893A at geociti=
es.com</A>&gt;...</DIV>Roland,=20
if you will...=20
<P>What is/will be the status on the contact list capability=20
(aw_contact_stuff)?&nbsp; I haven't noticed any talk about =
it.&nbsp; I'm=20
making a tour guide, and it would be really nice to have it =
inform me of=20
visitors while I am away, much less the other stuff I can do =
with=20
it...&nbsp; Seeing it in the API reference is like yummy candy =
in a=20
locked glass case! heh heh=20
<P>- &AElig;dificator =
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_009C_01BE5524.82AFDE60--

roland vilett

Feb 10, 1999, 5:44pm
This is a multi-part message in MIME format.

------=_NextPart_000_000D_01BE54EA.A6D4D8C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The file sending stuff you see in aw.h is only the requests that the =
browser uses to establish a file transfer session with another browser, =
since that part of the process occurs through the universe server. The =
guts of the peer-to-peer file transfer mechanism itself are not part of =
the SDK code, so even if these calls were available to an SDK app, you =
would still have to implement the actual file transfer part from =
scratch. Not very useful.

It's possible that we may include the entire file transfer mechanism in =
a future version of the SDK.

-Roland

[View Quote] - =C6dificator=20


------=_NextPart_000_000D_01BE54EA.A6D4D8C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!doctype html =
public "-//w3c//dtd html 4.0 transitional//en">
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>The file sending stuff you see in =
aw.h is only=20
the requests that the browser uses to establish a file transfer session =
with=20
another browser, since that part of the process occurs through the =
universe=20
server.&nbsp; The guts of the peer-to-peer file transfer mechanism =
itself are=20
not part of the SDK code, so even if these calls were available to an =
SDK app,=20
you would still have to implement the actual file transfer part from =
scratch.=20
Not very useful.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>It's possible that we may include the entire file =
transfer=20
mechanism in a future version of the SDK.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Roland</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
[View Quote] &lt;36c11d81.1 at homer&gt;...</DIV>
<DIV><FONT color=3D#000000 size=3D2>Unfortunately, supporting =
contact lists=20
from SDK apps will require some significant re-write of the =
contact=20
handling code in the uniserver.&nbsp; Currently the mechanism =
depends on=20
the owner of a contact list having a unique citizen number, so =
that will=20
have to be changed first.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Hopefully, we'll get this into a future =
version of=20
AW...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Roland</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
<DIV>&AElig;dificator<AEDIFICATOR~NOSPAM! at GEOCITIES.COM> =
wrote in=20
message &lt;<A=20
=
href=3D"mailto:36C116C8.3E00893A at geocities.com">36C116C8.3E00893A at geociti=
es.com</A>&gt;...</DIV>Roland,=20
if you will...=20
<P>What is/will be the status on the contact list capability =

(aw_contact_stuff)?&nbsp; I haven't noticed any talk about =
it.&nbsp;=20
I'm making a tour guide, and it would be really nice to have =
it=20
inform me of visitors while I am away, much less the other =
stuff I=20
can do with it...&nbsp; Seeing it in the API reference is =
like yummy=20
candy in a locked glass case! heh heh=20
<P>- &AElig;dificator =
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_000D_01BE54EA.A6D4D8C0--

walter knupe

Feb 11, 1999, 5:34pm
This is a multi-part message in MIME format.

------=_NextPart_000_0088_01BE55FD.FA31B100
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

And, is there any way to have a specification of the things needed to =
implement the file transfer from scratch ? i am sure all you do is =
negotiate some I.P. addresses and ports, transfer length and name, and =
then dump all the bytes into the socket until done..

thats not hard to do from scratch .)

all i need are some more details :)

Walter aka Faber

Roland Vilett schrieb in Nachricht <36c1e0ed.1 at homer>...
The file sending stuff you see in aw.h is only the requests that the =
browser uses to establish a file transfer session with another browser, =
since that part of the process occurs through the universe server. The =
guts of the peer-to-peer file transfer mechanism itself are not part of =
the SDK code, so even if these calls were available to an SDK app, you =
would still have to implement the actual file transfer part from =
scratch. Not very useful.
=20
It's possible that we may include the entire file transfer mechanism =
in a future version of the SDK.
=20
-Roland
=20
[View Quote] - =C6dificator=20


------=_NextPart_000_0088_01BE55FD.FA31B100
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 =
HTML//EN"><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN"><!DOCTYPE HTML =
PUBLIC "-//W3C//DTD W3 HTML//EN"><!doctype html public "-//w3c//dtd html =
4.0 transitional//en">
<META content=3D'"MSHTML 4.72.3511.1300"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT color=3D#000080>And, is =
there any way=20
to have a specification of the things needed to implement the file =
transfer from=20
scratch ? i am sure all you do is negotiate some I.P. addresses and =
ports,=20
transfer length and name, and then dump all the bytes into the socket =
until=20
done..</FONT></FONT><FONT color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT =
color=3D#000080></FONT></FONT><FONT=20
color=3D#000080></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT color=3D#000080>thats not =
hard to do=20
from scratch .)</FONT></FONT><FONT =
color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT =
color=3D#000080></FONT></FONT><FONT=20
color=3D#000080></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT color=3D#000080>all i =
need are some=20
more details :)</FONT></FONT><FONT =
color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT =
color=3D#000080></FONT></FONT><FONT=20
color=3D#000080></FONT></STRONG>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><STRONG><FONT color=3D#000080>Walter =
aka=20
Faber</FONT></FONT><FONT color=3D#000080></FONT></STRONG></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
<DIV>Roland Vilett<ROLAND at ACTIVEWORLDS.COM> schrieb in Nachricht=20
&lt;36c1e0ed.1 at homer&gt;...</DIV>
<DIV><FONT color=3D#000000 size=3D2>The file sending stuff you see =
in aw.h is=20
only the requests that the browser uses to establish a file transfer =
session=20
with another browser, since that part of the process occurs through =
the=20
universe server.&nbsp; The guts of the peer-to-peer file transfer =
mechanism=20
itself are not part of the SDK code, so even if these calls were =
available=20
to an SDK app, you would still have to implement the actual file =
transfer=20
part from scratch. Not very useful.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>It's possible that we may include the entire =
file transfer=20
mechanism in a future version of the SDK.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>-Roland</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">
[View Quote] ------=_NextPart_000_0088_01BE55FD.FA31B100--

1  |  
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn