dynapi-help — List relating to using the DynAPI, bug reports, and suggestions

Re: [Dynapi-Help] Simple communication questions...

[Leif W <war...@us...>]

This is going to be one of those revolutionary technologies that puts the
DynAPI over-the-top.  :)

Leif

----- Original Message ----- 
From: "Raymond Irving" <xw...@ya...>
To: <dyn...@li...>
Sent: Wednesday, October 15, 2003 4:14 PM
Subject: Re: [Dynapi-Help] Simple communication questions...


>
> In the DynAPI design sockets or http connections are
> not held or opened in definately. They're opened only
> for short periods of time (e.g. 50 secs) then released
> and reopened a few seconds later. This makes it
> posible to use both Push and Pull techniques to
> balance the connection load.
>
> The user (server-side) will have the option to adjust
> and balance the system while having the choice of
> using either push, pull or both.
>
> --
> Raymond Irving
>
> --- Leif W <war...@us...> wrote:
> > This looks very promising.  I've skimmed through the
> > whitepaper and a couple
> > example sources but can't seem to find exactly what
> > HTTP headers they're
> > sending, or if they're not doing the multipart hack
> > which is netscape and
> > mozilla specific, but instead just constantly
> > streaming code to an open
> > socket which appears to be what they're doing.
> >
> > Just wanted to point out what I think is the main
> > disadvantage of this
> > design, and reiterate and elaborate upon that point
> > just so it's understood
> > and maybe either find some way to work around, or at
> > least make sure we pass
> > on the warning to developers who may use our
> > library.  Using this technique
> > requires a socket to be constantly open between the
> > client and the server.
> > Normally, the browser makes a request, the socket is
> > used then released and
> > is free for the server to use to handle more
> > requests.  But with this
> > technique, the sockets will be used directly
> > proportional to the number of
> > users using the push, plus the number of users
> > otherwise requesting
> > documents on the server.  But most computers are
> > compiled with 65535 sockets
> > by default I believe.  I am not sure if any
> > operating systems allow for this
> > number to be increased.  I suspect that OSes like
> > Linux and FreeBSD would
> > allow this to be increased, by hacking the source
> > code.  It may or may not
> > be as trivial as changing a C language #define.
> > However it is done, having
> > achieved the proper modification and documented it,
> > recompiling the kernel
> > source is usually trivial for admin that keep their
> > software generally
> > unmodified and up to date, and who don't rely solely
> > on rpm or dselect to
> > handle everything, but it may not be trivial if they
> > have heavily modified
> > sources, dependent on third party code, or something
> > bizarre.  But be aware,
> > this may be in a shared hosting environment, or a
> > dedicated web server, may
> > be owned by the company that runs the hosting
> > provider, or by the company
> > that runs the web site.  The usage of this on a
> > moderate to high-traffic
> > site hosted on a machine that is currently handling
> > all it's requests with
> > plenty of socket overhead may hit a a resource
> > limitation which could affect
> > the whole server, which could be undesirable,
> > especially in a shared hosting
> > environment.  Also, there may be many levels of
> > management or ownership
> > between the web developer using this technique in
> > the DynAPI, and the admin
> > who would need to respond to the potential increased
> > resource requirements
> > if this technique were to be deployed on a
> > relatively high-traffic website.
> > Therefore I think it's imperative that we have some
> > sort of disclaimer on
> > the documentation page, and perhaps another page
> > with either notes to
> > increasing the number of sockets, or links to such
> > resources or something.
> >
> > Leif
> >
> > ----- Original Message ----- 
> > From: "Raymond Irving" <xw...@ya...>
> > To: <dyn...@li...>
> > Sent: Wednesday, October 15, 2003 11:34 AM
> > Subject: Re: [Dynapi-Help] Simple communication
> > questions...
> >
> >
> > >
> > > Wow!
> > >
> > > I've spend serveral hours looking into the
> > push/pull
> > > (pushlet) solution and must say that I have
> > managed to
> > > get a working prototype of the server-side push
> > > feature.
> > >
> > > I think it's possible that dynapi will be able to
> > > support both Push and/or Pull functionality. It's
> > > still a far way off and requires a lot of time to
> > > think through the design of the system (only if I
> > had
> > > a full time dynapi job :)
> > >
> > > In short I think it will be as simple as adding an
> > > event listener to a dynobject:
> > >
> > > io.addEventListener({
> > >    onserver_someventhere : function(e,s) {
> > >         // some code here
> > >    },
> > >    onserver_anothereventhere : function(e,s) {
> > >         // some code here
> > >    }
> > > });
> > >
> > > With this technology we could use ioelement with
> > any
> > > webserver or server-side language to implement the
> > > push and/or pull requests
> > >
> > > With the push method the client is notified
> > whenever
> > > the server invokes or raises an event:
> > >
> > > ws_invokeEvent('someeventhere')
> > > ...
> > > ws_invokeEvent('anothereventhere')
> > >
> > >
> > > The Push/Pull technique should work with all
> > supported
> > > web browsers. The API will handle all the
> > technical
> > > details so the user only have to listen in for an
> > > event from the server.
> > >
> > > What do you think?
> > >
> > >
> > > --
> > > Raymond Irving
> > >
> > >
> > >
> > > --- Andrew Gillett <an...@zo...> wrote:
> > > > This may be a little off-topic, but another
> > > > interesting site that's worth a look at is
> > > > www.pushlets.com.  Their basic setup is to use a
> > > > Java servlet to push javascript down a HTTP
> > > > connection to a hidden frame.  And they have
> > some
> > > > impressive demos :)  The claim compatability
> > with IE
> > > > (back to 4.01) and Netscape (back to 4.05).
> > > >
> > > > It would be _so impressive_ if an IOElement
> > could do
> > > > a similar thing....
> > > >
> > > >
> > > > Andrew Gillett
> > > >
> > > >
> > > > Raymond Irving wrote:
> > > > > Hi,
> > > > >
> > > > > For some more information on server-push and
> > > > > client-pull visit the following website:
> > > > >
> > > > >
> > > >
> > >
> >
> http://wp.netscape.com/assist/net_sites/pushpull.html
> > > > >
> > > > > --
> > > > > Raymond Irving
> > > > >
> > > > > --- Leif W <war...@us...> wrote:
> > > > >
> > > > >>I was thinking of how to approach this problem
> > a
> > > > >>while back (for the case of
> > > > >>a simple online cardgame) but never came to
> > > > anything
> > > > >>concrete.  However, I
> > > > >>did remember playing with some script (it was
> > in
> > > > >>Perl but you could use any
> > > > >>language) which acts as a server-push, but it
> > only
> > > > >>works for Mozilla, not
> > > > >>IE, and not tested in Opera or Safari.  So, if
> > you
> > > > >>want a true client-server
> > > > >>model with bidirectional communication I guess
> > > > >>you're best off coding a Java
> > > > >>applet for the browser, and whatever language
> > > > >>specialized server with your
> > > > >>own protocol.
> > > > >>
> > > > >>Anyways here's the example code I was using.
> > > > Also,
> >
> === message truncated ===
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>

Re: [Dynapi-Help] Simple communication questions...

[Raymond I. <xw...@ya...>]

In the DynAPI design sockets or http connections are
not held or opened in definately. They're opened only
for short periods of time (e.g. 50 secs) then released
and reopened a few seconds later. This makes it
posible to use both Push and Pull techniques to
balance the connection load.

The user (server-side) will have the option to adjust
and balance the system while having the choice of
using either push, pull or both.

--
Raymond Irving

--- Leif W <war...@us...> wrote:
> This looks very promising.  I've skimmed through the
> whitepaper and a couple
> example sources but can't seem to find exactly what
> HTTP headers they're
> sending, or if they're not doing the multipart hack
> which is netscape and
> mozilla specific, but instead just constantly
> streaming code to an open
> socket which appears to be what they're doing.
> 
> Just wanted to point out what I think is the main
> disadvantage of this
> design, and reiterate and elaborate upon that point
> just so it's understood
> and maybe either find some way to work around, or at
> least make sure we pass
> on the warning to developers who may use our
> library.  Using this technique
> requires a socket to be constantly open between the
> client and the server.
> Normally, the browser makes a request, the socket is
> used then released and
> is free for the server to use to handle more
> requests.  But with this
> technique, the sockets will be used directly
> proportional to the number of
> users using the push, plus the number of users
> otherwise requesting
> documents on the server.  But most computers are
> compiled with 65535 sockets
> by default I believe.  I am not sure if any
> operating systems allow for this
> number to be increased.  I suspect that OSes like
> Linux and FreeBSD would
> allow this to be increased, by hacking the source
> code.  It may or may not
> be as trivial as changing a C language #define. 
> However it is done, having
> achieved the proper modification and documented it,
> recompiling the kernel
> source is usually trivial for admin that keep their
> software generally
> unmodified and up to date, and who don't rely solely
> on rpm or dselect to
> handle everything, but it may not be trivial if they
> have heavily modified
> sources, dependent on third party code, or something
> bizarre.  But be aware,
> this may be in a shared hosting environment, or a
> dedicated web server, may
> be owned by the company that runs the hosting
> provider, or by the company
> that runs the web site.  The usage of this on a
> moderate to high-traffic
> site hosted on a machine that is currently handling
> all it's requests with
> plenty of socket overhead may hit a a resource
> limitation which could affect
> the whole server, which could be undesirable,
> especially in a shared hosting
> environment.  Also, there may be many levels of
> management or ownership
> between the web developer using this technique in
> the DynAPI, and the admin
> who would need to respond to the potential increased
> resource requirements
> if this technique were to be deployed on a
> relatively high-traffic website.
> Therefore I think it's imperative that we have some
> sort of disclaimer on
> the documentation page, and perhaps another page
> with either notes to
> increasing the number of sockets, or links to such
> resources or something.
> 
> Leif
> 
> ----- Original Message ----- 
> From: "Raymond Irving" <xw...@ya...>
> To: <dyn...@li...>
> Sent: Wednesday, October 15, 2003 11:34 AM
> Subject: Re: [Dynapi-Help] Simple communication
> questions...
> 
> 
> >
> > Wow!
> >
> > I've spend serveral hours looking into the
> push/pull
> > (pushlet) solution and must say that I have
> managed to
> > get a working prototype of the server-side push
> > feature.
> >
> > I think it's possible that dynapi will be able to
> > support both Push and/or Pull functionality. It's
> > still a far way off and requires a lot of time to
> > think through the design of the system (only if I
> had
> > a full time dynapi job :)
> >
> > In short I think it will be as simple as adding an
> > event listener to a dynobject:
> >
> > io.addEventListener({
> >    onserver_someventhere : function(e,s) {
> >         // some code here
> >    },
> >    onserver_anothereventhere : function(e,s) {
> >         // some code here
> >    }
> > });
> >
> > With this technology we could use ioelement with
> any
> > webserver or server-side language to implement the
> > push and/or pull requests
> >
> > With the push method the client is notified
> whenever
> > the server invokes or raises an event:
> >
> > ws_invokeEvent('someeventhere')
> > ...
> > ws_invokeEvent('anothereventhere')
> >
> >
> > The Push/Pull technique should work with all
> supported
> > web browsers. The API will handle all the
> technical
> > details so the user only have to listen in for an
> > event from the server.
> >
> > What do you think?
> >
> >
> > --
> > Raymond Irving
> >
> >
> >
> > --- Andrew Gillett <an...@zo...> wrote:
> > > This may be a little off-topic, but another
> > > interesting site that's worth a look at is
> > > www.pushlets.com.  Their basic setup is to use a
> > > Java servlet to push javascript down a HTTP
> > > connection to a hidden frame.  And they have
> some
> > > impressive demos :)  The claim compatability
> with IE
> > > (back to 4.01) and Netscape (back to 4.05).
> > >
> > > It would be _so impressive_ if an IOElement
> could do
> > > a similar thing....
> > >
> > >
> > > Andrew Gillett
> > >
> > >
> > > Raymond Irving wrote:
> > > > Hi,
> > > >
> > > > For some more information on server-push and
> > > > client-pull visit the following website:
> > > >
> > > >
> > >
> >
>
http://wp.netscape.com/assist/net_sites/pushpull.html
> > > >
> > > > --
> > > > Raymond Irving
> > > >
> > > > --- Leif W <war...@us...> wrote:
> > > >
> > > >>I was thinking of how to approach this problem
> a
> > > >>while back (for the case of
> > > >>a simple online cardgame) but never came to
> > > anything
> > > >>concrete.  However, I
> > > >>did remember playing with some script (it was
> in
> > > >>Perl but you could use any
> > > >>language) which acts as a server-push, but it
> only
> > > >>works for Mozilla, not
> > > >>IE, and not tested in Opera or Safari.  So, if
> you
> > > >>want a true client-server
> > > >>model with bidirectional communication I guess
> > > >>you're best off coding a Java
> > > >>applet for the browser, and whatever language
> > > >>specialized server with your
> > > >>own protocol.
> > > >>
> > > >>Anyways here's the example code I was using.
> > > Also,
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] Simple communication questions...

[Leif W <war...@us...>]

This looks very promising.  I've skimmed through the whitepaper and a couple
example sources but can't seem to find exactly what HTTP headers they're
sending, or if they're not doing the multipart hack which is netscape and
mozilla specific, but instead just constantly streaming code to an open
socket which appears to be what they're doing.

Just wanted to point out what I think is the main disadvantage of this
design, and reiterate and elaborate upon that point just so it's understood
and maybe either find some way to work around, or at least make sure we pass
on the warning to developers who may use our library.  Using this technique
requires a socket to be constantly open between the client and the server.
Normally, the browser makes a request, the socket is used then released and
is free for the server to use to handle more requests.  But with this
technique, the sockets will be used directly proportional to the number of
users using the push, plus the number of users otherwise requesting
documents on the server.  But most computers are compiled with 65535 sockets
by default I believe.  I am not sure if any operating systems allow for this
number to be increased.  I suspect that OSes like Linux and FreeBSD would
allow this to be increased, by hacking the source code.  It may or may not
be as trivial as changing a C language #define.  However it is done, having
achieved the proper modification and documented it, recompiling the kernel
source is usually trivial for admin that keep their software generally
unmodified and up to date, and who don't rely solely on rpm or dselect to
handle everything, but it may not be trivial if they have heavily modified
sources, dependent on third party code, or something bizarre.  But be aware,
this may be in a shared hosting environment, or a dedicated web server, may
be owned by the company that runs the hosting provider, or by the company
that runs the web site.  The usage of this on a moderate to high-traffic
site hosted on a machine that is currently handling all it's requests with
plenty of socket overhead may hit a a resource limitation which could affect
the whole server, which could be undesirable, especially in a shared hosting
environment.  Also, there may be many levels of management or ownership
between the web developer using this technique in the DynAPI, and the admin
who would need to respond to the potential increased resource requirements
if this technique were to be deployed on a relatively high-traffic website.
Therefore I think it's imperative that we have some sort of disclaimer on
the documentation page, and perhaps another page with either notes to
increasing the number of sockets, or links to such resources or something.

Leif

----- Original Message ----- 
From: "Raymond Irving" <xw...@ya...>
To: <dyn...@li...>
Sent: Wednesday, October 15, 2003 11:34 AM
Subject: Re: [Dynapi-Help] Simple communication questions...


>
> Wow!
>
> I've spend serveral hours looking into the push/pull
> (pushlet) solution and must say that I have managed to
> get a working prototype of the server-side push
> feature.
>
> I think it's possible that dynapi will be able to
> support both Push and/or Pull functionality. It's
> still a far way off and requires a lot of time to
> think through the design of the system (only if I had
> a full time dynapi job :)
>
> In short I think it will be as simple as adding an
> event listener to a dynobject:
>
> io.addEventListener({
>    onserver_someventhere : function(e,s) {
>         // some code here
>    },
>    onserver_anothereventhere : function(e,s) {
>         // some code here
>    }
> });
>
> With this technology we could use ioelement with any
> webserver or server-side language to implement the
> push and/or pull requests
>
> With the push method the client is notified whenever
> the server invokes or raises an event:
>
> ws_invokeEvent('someeventhere')
> ...
> ws_invokeEvent('anothereventhere')
>
>
> The Push/Pull technique should work with all supported
> web browsers. The API will handle all the technical
> details so the user only have to listen in for an
> event from the server.
>
> What do you think?
>
>
> --
> Raymond Irving
>
>
>
> --- Andrew Gillett <an...@zo...> wrote:
> > This may be a little off-topic, but another
> > interesting site that's worth a look at is
> > www.pushlets.com.  Their basic setup is to use a
> > Java servlet to push javascript down a HTTP
> > connection to a hidden frame.  And they have some
> > impressive demos :)  The claim compatability with IE
> > (back to 4.01) and Netscape (back to 4.05).
> >
> > It would be _so impressive_ if an IOElement could do
> > a similar thing....
> >
> >
> > Andrew Gillett
> >
> >
> > Raymond Irving wrote:
> > > Hi,
> > >
> > > For some more information on server-push and
> > > client-pull visit the following website:
> > >
> > >
> >
> http://wp.netscape.com/assist/net_sites/pushpull.html
> > >
> > > --
> > > Raymond Irving
> > >
> > > --- Leif W <war...@us...> wrote:
> > >
> > >>I was thinking of how to approach this problem a
> > >>while back (for the case of
> > >>a simple online cardgame) but never came to
> > anything
> > >>concrete.  However, I
> > >>did remember playing with some script (it was in
> > >>Perl but you could use any
> > >>language) which acts as a server-push, but it only
> > >>works for Mozilla, not
> > >>IE, and not tested in Opera or Safari.  So, if you
> > >>want a true client-server
> > >>model with bidirectional communication I guess
> > >>you're best off coding a Java
> > >>applet for the browser, and whatever language
> > >>specialized server with your
> > >>own protocol.
> > >>
> > >>Anyways here's the example code I was using.
> > Also,
> > >>I was testing on an
> > >>Apache server and the script would not work unless
> > >>the filename began with
> > >>"nph-" which stands for non-parsed headers.
> > >>
> > >>=============================
> > >>BEGIN - Perl script
> > >>=============================
> > >>#! /usr/bin/perl -w
> > >>use strict;
> > >>
> > >>use CGI qw/:standard :push/;
> > >>use CGI::Carp 'fatalsToBrowser';
> > >>
> > >>$CGI::POST_MAX = 1024 * 1024; # max 1M posts
> > >>$CGI::DISABLE_UPLOADS = 1;  # no uploads
> > >>$| = 1;
> > >>
> > >>print multipart_init(-boundary=>'----here we
> > go!');
> > >>
> > >>foreach (0 .. 4) {
> > >>    print multipart_start(-type=>'text/plain'),
> > >>          "The current time is
> > >>",scalar(localtime),"\n";
> > >>    if ($_ < 4) {
> > >>            print multipart_end;
> > >>    } else {
> > >>            print multipart_final;
> > >>    }
> > >>    sleep 1;
> > >>}
> > >>
> > >>=============================
> > >>END - Perl script
> > >>=============================
> > >>
> > >>As you can see, most of the actual server-push
> > code
> > >>is handled by the CGI
> > >>Perl Module.  So just taking a quick peek inside
> > to
> > >>show the relevent bits
> > >>of raw HTTP and HTML tricks used, or just using
> > >>telnet or wget to fetch from
> > >>the server.
> > >>
> > >>Headers: (first three added by Apache, last one
> > >>added by the script)
> > >>
> > >>HTTP/1.0 200 OK
> > >>Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47
> > >>OpenSSL/0.9.7c DAV/2
> > >>PHP/4.3.4RC1
> > >>Date: Tue, 14 Oct 2003 13:39:48 GMT
> > >>Content-Type:
> > >>multipart/x-mixed-replace;boundary="----here we
> > go!"
> > >>
> > >>Content:
> > >>
> > >>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> > >>SERVER-PUSH TECHNOLOGY.
> > >>------here we go!
> > >>Content-Type: text/plain
> > >>
> > >>The current time is Tue Oct 14 09:39:48 2003
> > >>
> > >>------here we go!
> > >>Content-Type: text/plain
> > >>
> > >>The current time is Tue Oct 14 09:39:49 2003
> > >>
> > >>------here we go!
> > >>Content-Type: text/plain
> > >>
> > >>The current time is Tue Oct 14 09:39:50 2003
> > >>
> > >>------here we go!
> > >>Content-Type: text/plain
> > >>
> > >>The current time is Tue Oct 14 09:39:51 2003
> > >>
> > >>------here we go!
> > >>Content-Type: text/plain
> > >>
> > >>The current time is Tue Oct 14 09:39:52 2003
> > >>
> > >>------here we go!--
> > >>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> > >>SERVER-PUSH TECHNOLOGY.
> > >>
> > >>
> > >>
> > >>----- Original Message ----- 
> > >>From: "Raymond Irving" <xw...@ya...>
> > >>To: <dyn...@li...>
> > >>Sent: Monday, October 13, 2003 10:27 AM
> > >>Subject: Re: [Dynapi-Help] Simple communication
> > >>questions...
> > >>
> > >>
> > >>
> > >>>See below:
> > >>>
> > >>>--- Clemens Eisserer <Lin...@we...> wrote:
> > >>>
> > >>>>Hi again!
> > >>>>
> > >>>>I´m currently thinking about writing a simple
> > >>>>JS-Chat, so that the chat doent need to reload
> > >>>>always when
> > >>>>new messages recieve.
> > >>>>The problem is, that the server should connect
> > >>
> > >>to
> > >>
> > >>>>the client, which is not possible as far as I
> > >>
> > >>know,
> > >>
> > >>>>this
> > >>>>means the client has to use possling and aks all
> > >>
> > >>x
> > >>
> > >>>>seconds the server for new messages.
> > >>>>
> > >>>>1.) Is there no other was to do this than
> > >>
> > >>polling?
> > >>
> > >>>Not that I know of
> > >>>
> > >>>
> > >>>>2.) These are the only polling-ideas I had:
> > >>>>* Blocking soda-rpc function. Blocks till
> > >>
> > >>messages
> > >>
> > >>>>are on server. (Problem with blocking - no
> > >>
> > >>events
> > >>
> > >>>>etc?)
> > >>>>* Non-Blocking soda-rpc function. Returns -1 if
> > >>>>nothing is there...
> > >>>>
> > >>>>Is the blocking version possible, or will it
> > >>
> > >>cause
> > >>
> > >>>>the application to hand in the poll-loop. This
> >
> === message truncated ===
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>

Re: [Dynapi-Help] Simple communication questions...

[Raymond I. <xw...@ya...>]

Wow!

I've spend serveral hours looking into the push/pull
(pushlet) solution and must say that I have managed to
get a working prototype of the server-side push
feature.

I think it's possible that dynapi will be able to
support both Push and/or Pull functionality. It's
still a far way off and requires a lot of time to
think through the design of the system (only if I had
a full time dynapi job :)

In short I think it will be as simple as adding an
event listener to a dynobject:

io.addEventListener({
   onserver_someventhere : function(e,s) {
        // some code here
   },
   onserver_anothereventhere : function(e,s) {
        // some code here
   }
}); 

With this technology we could use ioelement with any
webserver or server-side language to implement the
push and/or pull requests

With the push method the client is notified whenever
the server invokes or raises an event:

ws_invokeEvent('someeventhere')
...
ws_invokeEvent('anothereventhere')


The Push/Pull technique should work with all supported
web browsers. The API will handle all the technical
details so the user only have to listen in for an
event from the server. 

What do you think?


--
Raymond Irving



--- Andrew Gillett <an...@zo...> wrote:
> This may be a little off-topic, but another
> interesting site that's worth a look at is
> www.pushlets.com.  Their basic setup is to use a
> Java servlet to push javascript down a HTTP
> connection to a hidden frame.  And they have some
> impressive demos :)  The claim compatability with IE
> (back to 4.01) and Netscape (back to 4.05).
> 
> It would be _so impressive_ if an IOElement could do
> a similar thing....
> 
> 
> Andrew Gillett
> 
> 
> Raymond Irving wrote:
> > Hi,
> > 
> > For some more information on server-push and
> > client-pull visit the following website:
> > 
> >
>
http://wp.netscape.com/assist/net_sites/pushpull.html
> > 
> > --
> > Raymond Irving
> > 
> > --- Leif W <war...@us...> wrote:
> > 
> >>I was thinking of how to approach this problem a
> >>while back (for the case of
> >>a simple online cardgame) but never came to
> anything
> >>concrete.  However, I
> >>did remember playing with some script (it was in
> >>Perl but you could use any
> >>language) which acts as a server-push, but it only
> >>works for Mozilla, not
> >>IE, and not tested in Opera or Safari.  So, if you
> >>want a true client-server
> >>model with bidirectional communication I guess
> >>you're best off coding a Java
> >>applet for the browser, and whatever language
> >>specialized server with your
> >>own protocol.
> >>
> >>Anyways here's the example code I was using. 
> Also,
> >>I was testing on an
> >>Apache server and the script would not work unless
> >>the filename began with
> >>"nph-" which stands for non-parsed headers.
> >>
> >>=============================
> >>BEGIN - Perl script
> >>=============================
> >>#! /usr/bin/perl -w
> >>use strict;
> >>
> >>use CGI qw/:standard :push/;
> >>use CGI::Carp 'fatalsToBrowser';
> >>
> >>$CGI::POST_MAX = 1024 * 1024; # max 1M posts
> >>$CGI::DISABLE_UPLOADS = 1;  # no uploads
> >>$| = 1;
> >>
> >>print multipart_init(-boundary=>'----here we
> go!');
> >>
> >>foreach (0 .. 4) {
> >>    print multipart_start(-type=>'text/plain'),
> >>          "The current time is
> >>",scalar(localtime),"\n";
> >>    if ($_ < 4) {
> >>            print multipart_end;
> >>    } else {
> >>            print multipart_final;
> >>    }
> >>    sleep 1;
> >>}
> >>
> >>=============================
> >>END - Perl script
> >>=============================
> >>
> >>As you can see, most of the actual server-push
> code
> >>is handled by the CGI
> >>Perl Module.  So just taking a quick peek inside
> to
> >>show the relevent bits
> >>of raw HTTP and HTML tricks used, or just using
> >>telnet or wget to fetch from
> >>the server.
> >>
> >>Headers: (first three added by Apache, last one
> >>added by the script)
> >>
> >>HTTP/1.0 200 OK
> >>Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47
> >>OpenSSL/0.9.7c DAV/2
> >>PHP/4.3.4RC1
> >>Date: Tue, 14 Oct 2003 13:39:48 GMT
> >>Content-Type:
> >>multipart/x-mixed-replace;boundary="----here we
> go!"
> >>
> >>Content:
> >>
> >>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> >>SERVER-PUSH TECHNOLOGY.
> >>------here we go!
> >>Content-Type: text/plain
> >>
> >>The current time is Tue Oct 14 09:39:48 2003
> >>
> >>------here we go!
> >>Content-Type: text/plain
> >>
> >>The current time is Tue Oct 14 09:39:49 2003
> >>
> >>------here we go!
> >>Content-Type: text/plain
> >>
> >>The current time is Tue Oct 14 09:39:50 2003
> >>
> >>------here we go!
> >>Content-Type: text/plain
> >>
> >>The current time is Tue Oct 14 09:39:51 2003
> >>
> >>------here we go!
> >>Content-Type: text/plain
> >>
> >>The current time is Tue Oct 14 09:39:52 2003
> >>
> >>------here we go!--
> >>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> >>SERVER-PUSH TECHNOLOGY.
> >>
> >>
> >>
> >>----- Original Message ----- 
> >>From: "Raymond Irving" <xw...@ya...>
> >>To: <dyn...@li...>
> >>Sent: Monday, October 13, 2003 10:27 AM
> >>Subject: Re: [Dynapi-Help] Simple communication
> >>questions...
> >>
> >>
> >>
> >>>See below:
> >>>
> >>>--- Clemens Eisserer <Lin...@we...> wrote:
> >>>
> >>>>Hi again!
> >>>>
> >>>>I´m currently thinking about writing a simple
> >>>>JS-Chat, so that the chat doent need to reload
> >>>>always when
> >>>>new messages recieve.
> >>>>The problem is, that the server should connect
> >>
> >>to
> >>
> >>>>the client, which is not possible as far as I
> >>
> >>know,
> >>
> >>>>this
> >>>>means the client has to use possling and aks all
> >>
> >>x
> >>
> >>>>seconds the server for new messages.
> >>>>
> >>>>1.) Is there no other was to do this than
> >>
> >>polling?
> >>
> >>>Not that I know of
> >>>
> >>>
> >>>>2.) These are the only polling-ideas I had:
> >>>>* Blocking soda-rpc function. Blocks till
> >>
> >>messages
> >>
> >>>>are on server. (Problem with blocking - no
> >>
> >>events
> >>
> >>>>etc?)
> >>>>* Non-Blocking soda-rpc function. Returns -1 if
> >>>>nothing is there...
> >>>>
> >>>>Is the blocking version possible, or will it
> >>
> >>cause
> >>
> >>>>the application to hand in the poll-loop. This
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] Simple communication questions...

[Andrew G. <an...@zo...>]

This may be a little off-topic, but another interesting site that's worth=
 a look at is www.pushlets.com.  Their basic setup is to use a Java servl=
et to push javascript down a HTTP connection to a hidden frame.  And they=
 have some impressive demos :)  The claim compatability with IE (back to =
4.01) and Netscape (back to 4.05).

It would be _so impressive_ if an IOElement could do a similar thing....


Andrew Gillett


Raymond Irving wrote:
> Hi,
>=20
> For some more information on server-push and
> client-pull visit the following website:
>=20
> http://wp.netscape.com/assist/net_sites/pushpull.html
>=20
> --
> Raymond Irving
>=20
> --- Leif W <war...@us...> wrote:
>=20
>>I was thinking of how to approach this problem a
>>while back (for the case of
>>a simple online cardgame) but never came to anything
>>concrete.  However, I
>>did remember playing with some script (it was in
>>Perl but you could use any
>>language) which acts as a server-push, but it only
>>works for Mozilla, not
>>IE, and not tested in Opera or Safari.  So, if you
>>want a true client-server
>>model with bidirectional communication I guess
>>you're best off coding a Java
>>applet for the browser, and whatever language
>>specialized server with your
>>own protocol.
>>
>>Anyways here's the example code I was using.  Also,
>>I was testing on an
>>Apache server and the script would not work unless
>>the filename began with
>>"nph-" which stands for non-parsed headers.
>>
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>BEGIN - Perl script
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>#! /usr/bin/perl -w
>>use strict;
>>
>>use CGI qw/:standard :push/;
>>use CGI::Carp 'fatalsToBrowser';
>>
>>$CGI::POST_MAX =3D 1024 * 1024; # max 1M posts
>>$CGI::DISABLE_UPLOADS =3D 1;  # no uploads
>>$| =3D 1;
>>
>>print multipart_init(-boundary=3D>'----here we go!');
>>
>>foreach (0 .. 4) {
>>    print multipart_start(-type=3D>'text/plain'),
>>          "The current time is
>>",scalar(localtime),"\n";
>>    if ($_ < 4) {
>>            print multipart_end;
>>    } else {
>>            print multipart_final;
>>    }
>>    sleep 1;
>>}
>>
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>END - Perl script
>>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>>
>>As you can see, most of the actual server-push code
>>is handled by the CGI
>>Perl Module.  So just taking a quick peek inside to
>>show the relevent bits
>>of raw HTTP and HTML tricks used, or just using
>>telnet or wget to fetch from
>>the server.
>>
>>Headers: (first three added by Apache, last one
>>added by the script)
>>
>>HTTP/1.0 200 OK
>>Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47
>>OpenSSL/0.9.7c DAV/2
>>PHP/4.3.4RC1
>>Date: Tue, 14 Oct 2003 13:39:48 GMT
>>Content-Type:
>>multipart/x-mixed-replace;boundary=3D"----here we go!"
>>
>>Content:
>>
>>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
>>SERVER-PUSH TECHNOLOGY.
>>------here we go!
>>Content-Type: text/plain
>>
>>The current time is Tue Oct 14 09:39:48 2003
>>
>>------here we go!
>>Content-Type: text/plain
>>
>>The current time is Tue Oct 14 09:39:49 2003
>>
>>------here we go!
>>Content-Type: text/plain
>>
>>The current time is Tue Oct 14 09:39:50 2003
>>
>>------here we go!
>>Content-Type: text/plain
>>
>>The current time is Tue Oct 14 09:39:51 2003
>>
>>------here we go!
>>Content-Type: text/plain
>>
>>The current time is Tue Oct 14 09:39:52 2003
>>
>>------here we go!--
>>WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
>>SERVER-PUSH TECHNOLOGY.
>>
>>
>>
>>----- Original Message -----=20
>>From: "Raymond Irving" <xw...@ya...>
>>To: <dyn...@li...>
>>Sent: Monday, October 13, 2003 10:27 AM
>>Subject: Re: [Dynapi-Help] Simple communication
>>questions...
>>
>>
>>
>>>See below:
>>>
>>>--- Clemens Eisserer <Lin...@we...> wrote:
>>>
>>>>Hi again!
>>>>
>>>>I=B4m currently thinking about writing a simple
>>>>JS-Chat, so that the chat doent need to reload
>>>>always when
>>>>new messages recieve.
>>>>The problem is, that the server should connect
>>
>>to
>>
>>>>the client, which is not possible as far as I
>>
>>know,
>>
>>>>this
>>>>means the client has to use possling and aks all
>>
>>x
>>
>>>>seconds the server for new messages.
>>>>
>>>>1.) Is there no other was to do this than
>>
>>polling?
>>
>>>Not that I know of
>>>
>>>
>>>>2.) These are the only polling-ideas I had:
>>>>* Blocking soda-rpc function. Blocks till
>>
>>messages
>>
>>>>are on server. (Problem with blocking - no
>>
>>events
>>
>>>>etc?)
>>>>* Non-Blocking soda-rpc function. Returns -1 if
>>>>nothing is there...
>>>>
>>>>Is the blocking version possible, or will it
>>
>>cause
>>
>>>>the application to hand in the poll-loop. This
>>
>>is a
>>
>>>>problem
>>>>in my eyes since JS hasnt support f=FCr
>>
>>Multithreading
>>
>>>>:(
>>>
>>>Using synchronous GET or post will cause the app
>>
>>to
>>
>>>wait until the server returns a response.
>>>
>>>
>>>
>>>>Does anybody have better ideas, I=B4m not really
>>
>>happy
>>
>>>>with my stuff..
>>>
>>>In the future there might be an easier method
>>>
>>>--
>>>Raymond Irving
>>>
>>>
>>>>lg Clemens
>>>>
>>>>PS1: How hard would it be to adopt dynapi to
>>>>knoqueror? (only because it interrests me why so
>>>>many
>>>>examples dont work..)
>>>>PS2: Dynapi is great!
>>>>
>>>>
>>>

Re: [Dynapi-Help] Simple communication questions...

[Raymond I. <xw...@ya...>]

Hi,

For some more information on server-push and
client-pull visit the following website:

http://wp.netscape.com/assist/net_sites/pushpull.html

--
Raymond Irving

--- Leif W <war...@us...> wrote:
> I was thinking of how to approach this problem a
> while back (for the case of
> a simple online cardgame) but never came to anything
> concrete.  However, I
> did remember playing with some script (it was in
> Perl but you could use any
> language) which acts as a server-push, but it only
> works for Mozilla, not
> IE, and not tested in Opera or Safari.  So, if you
> want a true client-server
> model with bidirectional communication I guess
> you're best off coding a Java
> applet for the browser, and whatever language
> specialized server with your
> own protocol.
> 
> Anyways here's the example code I was using.  Also,
> I was testing on an
> Apache server and the script would not work unless
> the filename began with
> "nph-" which stands for non-parsed headers.
> 
> =============================
> BEGIN - Perl script
> =============================
> #! /usr/bin/perl -w
> use strict;
> 
> use CGI qw/:standard :push/;
> use CGI::Carp 'fatalsToBrowser';
> 
> $CGI::POST_MAX = 1024 * 1024; # max 1M posts
> $CGI::DISABLE_UPLOADS = 1;  # no uploads
> $| = 1;
> 
> print multipart_init(-boundary=>'----here we go!');
> 
> foreach (0 .. 4) {
>     print multipart_start(-type=>'text/plain'),
>           "The current time is
> ",scalar(localtime),"\n";
>     if ($_ < 4) {
>             print multipart_end;
>     } else {
>             print multipart_final;
>     }
>     sleep 1;
> }
> 
> =============================
> END - Perl script
> =============================
> 
> As you can see, most of the actual server-push code
> is handled by the CGI
> Perl Module.  So just taking a quick peek inside to
> show the relevent bits
> of raw HTTP and HTML tricks used, or just using
> telnet or wget to fetch from
> the server.
> 
> Headers: (first three added by Apache, last one
> added by the script)
> 
> HTTP/1.0 200 OK
> Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47
> OpenSSL/0.9.7c DAV/2
> PHP/4.3.4RC1
> Date: Tue, 14 Oct 2003 13:39:48 GMT
> Content-Type:
> multipart/x-mixed-replace;boundary="----here we go!"
> 
> Content:
> 
> WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> SERVER-PUSH TECHNOLOGY.
> ------here we go!
> Content-Type: text/plain
> 
> The current time is Tue Oct 14 09:39:48 2003
> 
> ------here we go!
> Content-Type: text/plain
> 
> The current time is Tue Oct 14 09:39:49 2003
> 
> ------here we go!
> Content-Type: text/plain
> 
> The current time is Tue Oct 14 09:39:50 2003
> 
> ------here we go!
> Content-Type: text/plain
> 
> The current time is Tue Oct 14 09:39:51 2003
> 
> ------here we go!
> Content-Type: text/plain
> 
> The current time is Tue Oct 14 09:39:52 2003
> 
> ------here we go!--
> WARNING: YOUR BROWSER DOESN'T SUPPORT THIS
> SERVER-PUSH TECHNOLOGY.
> 
> 
> 
> ----- Original Message ----- 
> From: "Raymond Irving" <xw...@ya...>
> To: <dyn...@li...>
> Sent: Monday, October 13, 2003 10:27 AM
> Subject: Re: [Dynapi-Help] Simple communication
> questions...
> 
> 
> >
> > See below:
> >
> > --- Clemens Eisserer <Lin...@we...> wrote:
> > > Hi again!
> > >
> > > I´m currently thinking about writing a simple
> > > JS-Chat, so that the chat doent need to reload
> > > always when
> > > new messages recieve.
> > > The problem is, that the server should connect
> to
> > > the client, which is not possible as far as I
> know,
> > > this
> > > means the client has to use possling and aks all
> x
> > > seconds the server for new messages.
> > >
> > > 1.) Is there no other was to do this than
> polling?
> >
> > Not that I know of
> >
> > > 2.) These are the only polling-ideas I had:
> > > * Blocking soda-rpc function. Blocks till
> messages
> > > are on server. (Problem with blocking - no
> events
> > > etc?)
> > > * Non-Blocking soda-rpc function. Returns -1 if
> > > nothing is there...
> > >
> > > Is the blocking version possible, or will it
> cause
> > > the application to hand in the poll-loop. This
> is a
> > > problem
> > > in my eyes since JS hasnt support für
> Multithreading
> > > :(
> >
> > Using synchronous GET or post will cause the app
> to
> > wait until the server returns a response.
> >
> >
> > > Does anybody have better ideas, I´m not really
> happy
> > > with my stuff..
> >
> > In the future there might be an easier method
> >
> > --
> > Raymond Irving
> >
> > > lg Clemens
> > >
> > > PS1: How hard would it be to adopt dynapi to
> > > knoqueror? (only because it interrests me why so
> > > many
> > > examples dont work..)
> > > PS2: Dynapi is great!
> > >
> > >
> >
>
____________________________________________________________________________
> __
> > > Zwei Mal Platz 1 mit dem jeweils besten
> > > Testergebnis! WEB.DE FreeMail
> > > und WEB.DE Club bei Stiftung Warentest!
> > > http://f.web.de/?mc=021183
> > >
> > >
> > >
> > >
> >
>
-------------------------------------------------------
> > > This SF.net email is sponsored by: SF.net
> Giveback
> > > Program.
> > > SourceForge.net hosts over 70,000 Open Source
> > > Projects.
> > > See the people who have HELPED US provide better
> > > services:
> > > Click here:
> http://sourceforge.net/supporters.php
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] Simple communication questions...

[Leif W <war...@us...>]

I was thinking of how to approach this problem a while back (for the case=
 of
a simple online cardgame) but never came to anything concrete.  However, =
I
did remember playing with some script (it was in Perl but you could use a=
ny
language) which acts as a server-push, but it only works for Mozilla, not
IE, and not tested in Opera or Safari.  So, if you want a true client-ser=
ver
model with bidirectional communication I guess you're best off coding a J=
ava
applet for the browser, and whatever language specialized server with you=
r
own protocol.

Anyways here's the example code I was using.  Also, I was testing on an
Apache server and the script would not work unless the filename began wit=
h
"nph-" which stands for non-parsed headers.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
BEGIN - Perl script
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
#! /usr/bin/perl -w
use strict;

use CGI qw/:standard :push/;
use CGI::Carp 'fatalsToBrowser';

$CGI::POST_MAX =3D 1024 * 1024; # max 1M posts
$CGI::DISABLE_UPLOADS =3D 1;  # no uploads
$| =3D 1;

print multipart_init(-boundary=3D>'----here we go!');

foreach (0 .. 4) {
    print multipart_start(-type=3D>'text/plain'),
          "The current time is ",scalar(localtime),"\n";
    if ($_ < 4) {
            print multipart_end;
    } else {
            print multipart_final;
    }
    sleep 1;
}

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
END - Perl script
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

As you can see, most of the actual server-push code is handled by the CGI
Perl Module.  So just taking a quick peek inside to show the relevent bit=
s
of raw HTTP and HTML tricks used, or just using telnet or wget to fetch f=
rom
the server.

Headers: (first three added by Apache, last one added by the script)

HTTP/1.0 200 OK
Server: Apache/2.0.47 (Unix) mod_ssl/2.0.47 OpenSSL/0.9.7c DAV/2
PHP/4.3.4RC1
Date: Tue, 14 Oct 2003 13:39:48 GMT
Content-Type: multipart/x-mixed-replace;boundary=3D"----here we go!"

Content:

WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.
------here we go!
Content-Type: text/plain

The current time is Tue Oct 14 09:39:48 2003

------here we go!
Content-Type: text/plain

The current time is Tue Oct 14 09:39:49 2003

------here we go!
Content-Type: text/plain

The current time is Tue Oct 14 09:39:50 2003

------here we go!
Content-Type: text/plain

The current time is Tue Oct 14 09:39:51 2003

------here we go!
Content-Type: text/plain

The current time is Tue Oct 14 09:39:52 2003

------here we go!--
WARNING: YOUR BROWSER DOESN'T SUPPORT THIS SERVER-PUSH TECHNOLOGY.



----- Original Message -----=20
From: "Raymond Irving" <xw...@ya...>
To: <dyn...@li...>
Sent: Monday, October 13, 2003 10:27 AM
Subject: Re: [Dynapi-Help] Simple communication questions...


>
> See below:
>
> --- Clemens Eisserer <Lin...@we...> wrote:
> > Hi again!
> >
> > I=B4m currently thinking about writing a simple
> > JS-Chat, so that the chat doent need to reload
> > always when
> > new messages recieve.
> > The problem is, that the server should connect to
> > the client, which is not possible as far as I know,
> > this
> > means the client has to use possling and aks all x
> > seconds the server for new messages.
> >
> > 1.) Is there no other was to do this than polling?
>
> Not that I know of
>
> > 2.) These are the only polling-ideas I had:
> > * Blocking soda-rpc function. Blocks till messages
> > are on server. (Problem with blocking - no events
> > etc?)
> > * Non-Blocking soda-rpc function. Returns -1 if
> > nothing is there...
> >
> > Is the blocking version possible, or will it cause
> > the application to hand in the poll-loop. This is a
> > problem
> > in my eyes since JS hasnt support f=FCr Multithreading
> > :(
>
> Using synchronous GET or post will cause the app to
> wait until the server returns a response.
>
>
> > Does anybody have better ideas, I=B4m not really happy
> > with my stuff..
>
> In the future there might be an easier method
>
> --
> Raymond Irving
>
> > lg Clemens
> >
> > PS1: How hard would it be to adopt dynapi to
> > knoqueror? (only because it interrests me why so
> > many
> > examples dont work..)
> > PS2: Dynapi is great!
> >
> >
>
_________________________________________________________________________=
___
__
> > Zwei Mal Platz 1 mit dem jeweils besten
> > Testergebnis! WEB.DE FreeMail
> > und WEB.DE Club bei Stiftung Warentest!
> > http://f.web.de/?mc=3D021183
> >
> >
> >
> >
> -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback
> > Program.
> > SourceForge.net hosts over 70,000 Open Source
> > Projects.
> > See the people who have HELPED US provide better
> > services:
> > Click here: http://sourceforge.net/supporters.php
> > _______________________________________________
> > Dynapi-Help mailing list
> > Dyn...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>

Re: [Dynapi-Help] Simple communication questions...

[Raymond I. <xw...@ya...>]

See below:

--- Clemens Eisserer <Lin...@we...> wrote:
> Hi again! 
>  
> I´m currently thinking about writing a simple
> JS-Chat, so that the chat doent need to reload
> always when 
> new messages recieve. 
> The problem is, that the server should connect to
> the client, which is not possible as far as I know,
> this 
> means the client has to use possling and aks all x
> seconds the server for new messages. 
>  
> 1.) Is there no other was to do this than polling? 

Not that I know of
  
> 2.) These are the only polling-ideas I had: 
> * Blocking soda-rpc function. Blocks till messages
> are on server. (Problem with blocking - no events
> etc?) 
> * Non-Blocking soda-rpc function. Returns -1 if
> nothing is there... 
>  
> Is the blocking version possible, or will it cause
> the application to hand in the poll-loop. This is a
> problem 
> in my eyes since JS hasnt support für Multithreading
> :( 

Using synchronous GET or post will cause the app to
wait until the server returns a response. 


> Does anybody have better ideas, I´m not really happy
> with my stuff.. 

In the future there might be an easier method

--
Raymond Irving

> lg Clemens 
>  
> PS1: How hard would it be to adopt dynapi to
> knoqueror? (only because it interrests me why so
> many 
> examples dont work..) 
> PS2: Dynapi is great! 
>  
>
______________________________________________________________________________
> Zwei Mal Platz 1 mit dem jeweils besten
> Testergebnis! WEB.DE FreeMail
> und WEB.DE Club bei Stiftung Warentest!
> http://f.web.de/?mc=021183
> 
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback
> Program.
> SourceForge.net hosts over 70,000 Open Source
> Projects.
> See the people who have HELPED US provide better
> services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
>
https://lists.sourceforge.net/lists/listinfo/dynapi-help


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[Dynapi-Help] DynAPI updates

[Raymond I. <xw...@ya...>]

[*] Updated Documentation & Examples
[*] Update quickrefs (See docs/docs/quickref.html)
[+] Added new examples 
[+] Add DragIcon feature to DragEvent
[*] Modify DragDrop() events to use mouse pointer or
layer's width/height
[*] Move Frame Class from BorderManager into frame.js
file - dynapi.gui.Frame
[+] Add setBorder(w,c,style) to BorderManager - see
dynapi.gui.bordermanager-boxfix.html
[-] Add box fix model to dynlayers (requires
BorderManager).

Changes are now inside CVS or you can download the
latest snapshot


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[Dynapi-Help] Simple communication questions...

[Clemens E. <Lin...@we...>]

Hi again!=20
=20
I=B4m currently thinking about writing a simple JS-Chat, so that the chat do=
ent need to reload always when=20
new messages recieve.=20
The problem is, that the server should connect to the client, which is not=
 possible as far as I know, this=20
means the client has to use possling and aks all x seconds the server for =
new messages.=20
=20
1.) Is there no other was to do this than polling=3F=20
=20
2.) These are the only polling-ideas I had:=20
* Blocking soda-rpc function. Blocks till messages are on server. (Problem=
 with blocking - no events etc=3F)=20
* Non-Blocking soda-rpc function. Returns -1 if nothing is there...=20
=20
Is the blocking version possible, or will it cause the application to hand=
 in the poll-loop. This is a problem=20
in my eyes since JS hasnt support f=FCr Multithreading :(=20
=20
Does anybody have better ideas, I=B4m not really happy with my stuff..=20
=20
lg Clemens=20
=20
PS1: How hard would it be to adopt dynapi to knoqueror=3F (only because it i=
nterrests me why so many=20
examples dont work..)=20
PS2: Dynapi is great!=20
=20
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F
Zwei Mal Platz 1 mit dem jeweils besten Testergebnis! WEB.DE FreeMail
und WEB.DE Club bei Stiftung Warentest! http://f.web.de/=3Fmc=3D021183

Re: [Dynapi-Help] How DTDs effect IE 6 and Mozilla 1.5 on Windows (HTMLMenu)

[Bruce T. <blu...@ya...>]

Well it has been over 10 hours and my email seems not to have made it
through.

Here are the fixes for HTMLMenu that makes Mozilla work w/all DTD
specifications.  As I mentioned before, IE has bug w/the getHeight
function under some DTDs.  The bug causes the
dynapi.document.getHeight() call to return 0 and makes auto-fold
sub-menus section fail.

Here's the diff: 
diff src/gui/htmlmenu.js.orig src/gui/htmlmenu.js
 
118c118
<                       str += '<div id="' + itemID + '"
onclick="return '+this+'._e(\'click\','+currMenu+','+currItem+')"
style="position: absolute; left: ' + itemX + '; top: ' + itemY + ';
width: ' + w + '; height: ' + h + '; visibility: inherit; ';
---
>                       str += '<div id="' + itemID + '"
onclick="return '+this+'._e(\'click\','+currMenu+','+currItem+')"
style="position: absolute; left: ' + itemX + 'px; top: ' + itemY + 'px;
width: ' + w + 'px; height: ' + h + 'px; visibility: inherit; ';
262,263c262,263
<                               left = thisX;
<                               top = thisY;
---
>                               left = thisX +'px';
>                               top = thisY +'px';


--- Bruce Tennant <blu...@ya...> wrote:
> Well I fixed it for Mozilla (added the px units to a couple spots). 
> It
> fixed it for all of the DTDs for Mozilla, but there is a bug in the
> dynapi.document.getHeight that is causing the IE errors listed below.
> 
> An email w/the htmlmenu.js diff and new file should be coming... I
> sent
> it a few hours ago.
> 
> --- Dan Willemsen <dy...@da...> wrote:
> > my guess is that when it doesn't work, mozilla is in it's 'full
> > standards' html rendering mode, which just means that it doesn't
> try
> > to
> > fix common mistakes by html writers, etc.
> > 
> > To find out whether a page is in full standards mode, click
> > View->Page
> > Info, and look at the Rendering Mode.
> > 
> > Here is a good listing of which doctypes are in which mode:
> > 
> > http://www.mozilla.org/docs/web-developer/quirks/doctypes.html
> > 
> > There are also a few good articles on DevEdge about the different
> > modes:
> > 
> > http://devedge.netscape.com/viewsource/2002/almost-standards/
> > 
> > http://devedge.netscape.com/viewsource/2002/img-table/
> > 
> > http://www.mozilla.org/docs/web-developer/quirks/
> > 
> > Dan Willemsen
> > 
> > On Sat, 2003-10-11 at 15:58, Bruce Tennant wrote:
> > > Using the HTMLMenu example, I ran through the different DTDs and
> > here
> > > is a summary of what I found.
> > > 
> > > When IE fails, the top menu is displayed correctly, but the sub
> > menus
> > > collapse and go up rather than down.
> > > 
> > > When Mozilla fails, the top menu collapses and makes it hard to
> see
> > > what the sub menus do. My guess is collapse and jump off to the
> far
> > > left.
> > > 
> > > 
> > > #####  Works in IE and Mozilla
> > > ########################################
> > > No DTD given (both in default modes (quirks mode))
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > > 
> > > #####  Works in IE and NOT Mozilla
> > > ########################################
> > > 
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
> > >                      
> > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> > > 
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> > >                      
> > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> > > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">
> > > 
> > > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HTML//EN">
> > > 
> > > #####  Works in Mozilla and NOT IE
> > > ########################################
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 
> > >                       "http://www.w3.org/TR/html4/loose.dtd">
> > > 
> > > 
> > > #####  Does NOT Work in Mozilla or IE
> > > ########################################
> > > 
> > > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> > >                       "http://www.w3.org/TR/html4/loose.dtd">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" 
> > >                       "http://www.w3.org/TR/html4/strict.dtd">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
> > >                       "http://www.w3.org/TR/html4/strict.dtd">
> > > 
> > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
> > >                      
> > > "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
> > > 
> > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
> > >                      
> > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> > > 
> > > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> > >                      
> > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> > > 
> > > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup
> > > Language//EN">
> > > 
> > > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HyperText Markup
> > > Language//EN">
> > 
> > -- 
> > Dan Willemsen <dy...@da...>
> > 
> > 
> > -------------------------------------------------------
> > This SF.net email is sponsored by: SF.net Giveback Program.
> > SourceForge.net hosts over 70,000 Open Source Projects.
> > See the people who have HELPED US provide better services:
> > Click here: http://sourceforge.net/supporters.php
> > _______________________________________________
> > Dynapi-Help mailing list
> > Dyn...@li...
> > https://lists.sourceforge.net/lists/listinfo/dynapi-help
> 
> 
> =====
> www.bluewolverine.com
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help


=====
www.bluewolverine.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] How DTDs effect IE 6 and Mozilla 1.5 on Windows (HTMLMenu)

[Bruce T. <blu...@ya...>]

Well I fixed it for Mozilla (added the px units to a couple spots).  It
fixed it for all of the DTDs for Mozilla, but there is a bug in the
dynapi.document.getHeight that is causing the IE errors listed below.

An email w/the htmlmenu.js diff and new file should be coming... I sent
it a few hours ago.

--- Dan Willemsen <dy...@da...> wrote:
> my guess is that when it doesn't work, mozilla is in it's 'full
> standards' html rendering mode, which just means that it doesn't try
> to
> fix common mistakes by html writers, etc.
> 
> To find out whether a page is in full standards mode, click
> View->Page
> Info, and look at the Rendering Mode.
> 
> Here is a good listing of which doctypes are in which mode:
> 
> http://www.mozilla.org/docs/web-developer/quirks/doctypes.html
> 
> There are also a few good articles on DevEdge about the different
> modes:
> 
> http://devedge.netscape.com/viewsource/2002/almost-standards/
> 
> http://devedge.netscape.com/viewsource/2002/img-table/
> 
> http://www.mozilla.org/docs/web-developer/quirks/
> 
> Dan Willemsen
> 
> On Sat, 2003-10-11 at 15:58, Bruce Tennant wrote:
> > Using the HTMLMenu example, I ran through the different DTDs and
> here
> > is a summary of what I found.
> > 
> > When IE fails, the top menu is displayed correctly, but the sub
> menus
> > collapse and go up rather than down.
> > 
> > When Mozilla fails, the top menu collapses and makes it hard to see
> > what the sub menus do. My guess is collapse and jump off to the far
> > left.
> > 
> > 
> > #####  Works in IE and Mozilla
> > ########################################
> > No DTD given (both in default modes (quirks mode))
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> > 
> > #####  Works in IE and NOT Mozilla
> > ########################################
> > 
> > <?xml version="1.0" encoding="UTF-8"?>
> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
> >                      
> > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> > 
> > <?xml version="1.0" encoding="UTF-8"?>
> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> >                      
> > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">
> > 
> > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HTML//EN">
> > 
> > #####  Works in Mozilla and NOT IE
> > ########################################
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 
> >                       "http://www.w3.org/TR/html4/loose.dtd">
> > 
> > 
> > #####  Does NOT Work in Mozilla or IE
> > ########################################
> > 
> > <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
> >                       "http://www.w3.org/TR/html4/loose.dtd">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" 
> >                       "http://www.w3.org/TR/html4/strict.dtd">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
> >                       "http://www.w3.org/TR/html4/strict.dtd">
> > 
> > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
> >                      
> > "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
> > 
> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
> >                      
> > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> > 
> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> >                      
> > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> > 
> > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup
> > Language//EN">
> > 
> > <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HyperText Markup
> > Language//EN">
> 
> -- 
> Dan Willemsen <dy...@da...>
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help


=====
www.bluewolverine.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] How DTDs effect IE 6 and Mozilla 1.5 on Windows (HTMLMenu)

[Dan W. <dy...@da...>]

my guess is that when it doesn't work, mozilla is in it's 'full
standards' html rendering mode, which just means that it doesn't try to
fix common mistakes by html writers, etc.

To find out whether a page is in full standards mode, click View->Page
Info, and look at the Rendering Mode.

Here is a good listing of which doctypes are in which mode:

http://www.mozilla.org/docs/web-developer/quirks/doctypes.html

There are also a few good articles on DevEdge about the different modes:

http://devedge.netscape.com/viewsource/2002/almost-standards/

http://devedge.netscape.com/viewsource/2002/img-table/

http://www.mozilla.org/docs/web-developer/quirks/

Dan Willemsen

On Sat, 2003-10-11 at 15:58, Bruce Tennant wrote:
> Using the HTMLMenu example, I ran through the different DTDs and here
> is a summary of what I found.
> 
> When IE fails, the top menu is displayed correctly, but the sub menus
> collapse and go up rather than down.
> 
> When Mozilla fails, the top menu collapses and makes it hard to see
> what the sub menus do. My guess is collapse and jump off to the far
> left.
> 
> 
> #####  Works in IE and Mozilla
> ########################################
> No DTD given (both in default modes (quirks mode))
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> 
> #####  Works in IE and NOT Mozilla
> ########################################
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HTML//EN">
> 
> #####  Works in Mozilla and NOT IE
> ########################################
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 
>                       "http://www.w3.org/TR/html4/loose.dtd">
> 
> 
> #####  Does NOT Work in Mozilla or IE
> ########################################
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>                       "http://www.w3.org/TR/html4/loose.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" 
>                       "http://www.w3.org/TR/html4/strict.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
>                       "http://www.w3.org/TR/html4/strict.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
>                      
> "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup
> Language//EN">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HyperText Markup
> Language//EN">

-- 
Dan Willemsen <dy...@da...>

[Dynapi-Help] Can you apply CSS from file to HTMLMenu?

[Bruce T. <blu...@ya...>]

I don't seem to be able to define a css style in a file (using link)
and have it apply to the HTMLMenu component (the link line is prior to
the menu def script block).

Is this not possible?

Also, I tried to do the HTMLComponent.writeStyle technique as in the
examples, but Mozilla never seems to see these (IE did).

Thanks for any help,

-Bruce


=====
www.bluewolverine.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[Dynapi-Help] [FIX] Re: How DTDs effect IE 6 and Mozilla 1.5 on Windows (HTMLMenu)

[Bruce T. <blu...@ya...>]

Here's the fix for HTMLMenu.

It works for all of the Mozilla failures, but none of the IE.  The IE
failures appear to be a failure in the sub menu folding code because
the dynapi.document.getHeight() function is returning 0.

here's the diff (attached is the whole fixed file)

Index: src/gui/htmlmenu.js
===================================================================
RCS file: /cvsroot/dynapi/dynapi3x/src/gui/htmlmenu.js,v
retrieving revision 1.10
diff -r1.10 htmlmenu.js
118c118
<                       str += '<div id="' + itemID + '"
onclick="return '+this+'._e(\'click\','+currMenu+','+currItem+')"
style="position: absolute; left: ' + itemX + '; top: ' + itemY + ';
width: ' + w + '; height: ' + h + '; visibility: inherit; ';
---
>                       str += '<div id="' + itemID + '"
onclick="return '+this+'._e(\'click\','+currMenu+','+currItem+')"
style="position: absolute; left: ' + itemX + 'px; top: ' + itemY + 'px;
width: ' + w + 'px; height: ' + h + 'px; visibility: inherit; ';
262,263c262,263
<                               left = thisX;
<                               top = thisY;
---
>                               left = thisX +'px';
>                               top = thisY +'px';


--- Bruce Tennant <blu...@ya...> wrote:
> Using the HTMLMenu example, I ran through the different DTDs and here
> is a summary of what I found.
>  
> When IE fails, the top menu is displayed correctly, but the sub menus
> collapse and go up rather than down.
>  
> When Mozilla fails, the top menu collapses and makes it hard to see
> what the sub menus do.  My guess is collapse and jump off to the far
> left.
>  
>  
> #####  Works in IE and Mozilla
> ########################################
> No DTD given (both in default modes (quirks mode))
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> 
> #####  Works in IE and NOT Mozilla
> ########################################
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HTML//EN">
> 
> #####  Works in Mozilla and NOT IE
> ########################################
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 
>                       "http://www.w3.org/TR/html4/loose.dtd">
> 
> 
> #####  Does NOT Work in Mozilla or IE
> ########################################
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
>                       "http://www.w3.org/TR/html4/loose.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" 
>                       "http://www.w3.org/TR/html4/strict.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
>                       "http://www.w3.org/TR/html4/strict.dtd">
> 
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
>                      
> "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
> 
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>                      
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup
> Language//EN">
> 
> <!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HyperText Markup
> Language//EN">
> 
> 
> 
> 
> =====
> www.bluewolverine.com
> 
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> Dynapi-Help mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynapi-help


=====
www.bluewolverine.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

[Dynapi-Help] How DTDs effect IE 6 and Mozilla 1.5 on Windows (HTMLMenu)

[Bruce T. <blu...@ya...>]

Using the HTMLMenu example, I ran through the different DTDs and here
is a summary of what I found.
 
When IE fails, the top menu is displayed correctly, but the sub menus
collapse and go up rather than down.
 
When Mozilla fails, the top menu collapses and makes it hard to see
what the sub menus do.  My guess is collapse and jump off to the far
left.
 
 
#####  Works in IE and Mozilla
########################################
No DTD given (both in default modes (quirks mode))

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

#####  Works in IE and NOT Mozilla
########################################

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
                     
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
                     
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HTML//EN">

<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HTML//EN">

#####  Works in Mozilla and NOT IE
########################################

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" 
                      "http://www.w3.org/TR/html4/loose.dtd">


#####  Does NOT Work in Mozilla or IE
########################################

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
                      "http://www.w3.org/TR/html4/loose.dtd">

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

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" 
                      "http://www.w3.org/TR/html4/strict.dtd">

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" 
                      "http://www.w3.org/TR/html4/strict.dtd">

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 
                     
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
                     
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
                     
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:2000//DTD HyperText Markup
Language//EN">

<!DOCTYPE HTML PUBLIC "ISO/IEC 15445:1999//DTD HyperText Markup
Language//EN">




=====
www.bluewolverine.com

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu

[Bruce T. <blu...@ya...>]

I think it has something to do with when to use "px" unit identifiers.  I went poking in the htmlmenu.js source file and I was able to get the top level menu to display properly by adding the px to all of the width/height attributes.  But the submenus started jumping off to the side.  So I didn't fix it, but I think I found the root of the problem.  I knew to look here as I've had problems w/CSS definitions that didn't include the px.  This seems to be a Mozilla thing.  Is Mozilla just actually following the "strict" sense?  if so, then it isn't following the transient/loose dtd indicators.

Leif W <war...@us...> wrote:I had noticed the same thing also, regarding the Transitional. I was making
some test page for something and was trying to be "proper" and put all the
"proper" doctypes in place. But it broke something. Not sure why. But as
far as the XHTML goes, I know one major difference is that all tags must
terminate. If they have no closing tag, like 
or  [input] , then it's
supposed to be 
and  [input] , etc. But I've not read up on the
differences at the W3C.

Leif

----- Original Message ----- 
From: Bruce Tennant
To: dyn...@li...
Sent: Friday, October 10, 2003 7:50 PM
Subject: Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu


This causes the same problem too.


PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">

Bruce Tennant wrote:
When using XHTML 1.0 standard, Mozilla seems to collapse all of the menu
items on top of each other (HTMLMenu component).

IE 6 works fine, Mozilla 1.5 for Windows doesn't.

Here are the header lines used, you can add them to the example and see what
I'm talking about.


PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


Don't know if this is something DynAPI should address or not.


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Dynapi-Help mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapi-help


www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu

[Bruce T. <blu...@ya...>]

The dtd for html 3.2 works.
 
I messed with strict and loose and stuff, none of the 4.x and XHTML dtd's worked w/Mozilla and HTMLmenu.
 
Here's a site I found that lists a bunch of the possibilities, I'm not sure it is current for Mozilla 1.4/5 though.
 
http://www.hut.fi/u/hsivonen/doctype.html

Leif W <war...@us...> wrote:
I had noticed the same thing also, regarding the Transitional. I was making
some test page for something and was trying to be "proper" and put all the
"proper" doctypes in place. But it broke something. Not sure why. But as
far as the XHTML goes, I know one major difference is that all tags must
terminate. If they have no closing tag, like 
or  [input] , then it's
supposed to be 
and  [input] , etc. But I've not read up on the
differences at the W3C.

Leif

----- Original Message ----- 
From: Bruce Tennant
To: dyn...@li...
Sent: Friday, October 10, 2003 7:50 PM
Subject: Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu


This causes the same problem too.


PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">

Bruce Tennant wrote:
When using XHTML 1.0 standard, Mozilla seems to collapse all of the menu
items on top of each other (HTMLMenu component).

IE 6 works fine, Mozilla 1.5 for Windows doesn't.

Here are the header lines used, you can add them to the example and see what
I'm talking about.


PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


Don't know if this is something DynAPI should address or not.


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Dynapi-Help mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapi-help

www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu

[Leif W <war...@us...>]

I had noticed the same thing also, regarding the Transitional.  I was making
some test page for something and was trying to be "proper" and put all the
"proper" doctypes in place.  But it broke something.  Not sure why.  But as
far as the XHTML goes, I know one major difference is that all tags must
terminate.  If they have no closing tag, like <BR> or <INPUT>, then it's
supposed to be <BR /> and <INPUT />, etc.  But I've not read up on the
differences at the W3C.

Leif

----- Original Message ----- 
From: Bruce Tennant
To: dyn...@li...
Sent: Friday, October 10, 2003 7:50 PM
Subject: Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu


This causes the same problem too.


<!DOCTYPE html
 PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
  "http://www.w3.org/TR/html4/loose.dtd">

Bruce Tennant <blu...@ya...> wrote:
When using  XHTML 1.0 standard, Mozilla seems to collapse all of the menu
items on top of each other (HTMLMenu component).

IE 6 works fine, Mozilla 1.5 for Windows doesn't.

Here are the header lines used, you can add them to the example and see what
I'm talking about.

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


Don't know if this is something DynAPI should address or not.


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


www.bluewolverine.com


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Re: [Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu

[Bruce T. <blu...@ya...>]

This causes the same problem too.
 

<!DOCTYPE html
 PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
  "http://www.w3.org/TR/html4/loose.dtd">

Bruce Tennant <blu...@ya...> wrote:
When using  XHTML 1.0 standard, Mozilla seems to collapse all of the menu items on top of each other (HTMLMenu component).
 
IE 6 works fine, Mozilla 1.5 for Windows doesn't.
 
Here are the header lines used, you can add them to the example and see what I'm talking about.
 
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

 
Don't know if this is something DynAPI should address or not.


www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

[Dynapi-Help] perlsCGI.pm XML header casues greif for HTMLMenu

[Bruce T. <blu...@ya...>]

When using  XHTML 1.0 standard, Mozilla seems to collapse all of the menu items on top of each other (HTMLMenu component).
 
IE 6 works fine, Mozilla 1.5 for Windows doesn't.
 
Here are the header lines used, you can add them to the example and see what I'm talking about.
 
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
 PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

 
Don't know if this is something DynAPI should address or not.


www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

[Dynapi-Help] Change ondrop to ondragdrop

[Raymond I. <xw...@ya...>]

Hi Everyone,

I think I've made a mistake with the event names. In
keeping with ondragstart, ondragmove, ondragend,
ondragover we should change ondrop to ondragdrop

Everyone in agreement?

PS. Some newer changes are coming that enable you to
do some great drag and drop features that is not easy
to do without DynAPI :)


--
Raymond Irving.


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

Re: [Dynapi-Help] PanelBar and auto sizing

[Andrew G. <an...@zo...>]

Hi Bruce,

I had a similar requirement, an my "quick& dirty" solution
was to modify the PanelBar widget and subclass it.  See:
http://www.mail-archive.com/dyn...@li.../msg05775.html

Raymond subsequently suggested using the DynLayer "setAutoSize"
function to achieve the same effect, but I haven't been able to
get this to work yet.


Andrew Gillett


Bruce Tennant wrote:
> Now that I have my web app up and running w/old fashion HTML/CGI 
> techniques, I've decided to start phasing in some DHTML using DynAPI.
>  
> One thing I was trying to do is change a list of tables into a 
> stacker-panelbar combo.  The tables aren't all the same size, so I can't 
> reliably use a fixed height.  Is there anyway to get panelbar to auto 
> size (in the height direction mainly)?
>  
> Also, can it be done without building the stacker/panels in the head 
> section (built in body).  Currently the stacker/panels work attached to 
> an inline Dynlayer and built within the body. But I need to use a fixed 
> height for the panel content.
>  
> Thanks for any advise.
>  
> -Bruce
>  
> 
> 
> www.bluewolverine.com
> 
> ------------------------------------------------------------------------
> Do you Yahoo!?
> The New Yahoo! Shopping 
> <http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail> 
> - with improved product search

[Dynapi-Help] PanelBar and auto sizing

[Bruce T. <blu...@ya...>]

Now that I have my web app up and running w/old fashion HTML/CGI techniques, I've decided to start phasing in some DHTML using DynAPI.
 
One thing I was trying to do is change a list of tables into a stacker-panelbar combo.  The tables aren't all the same size, so I can't reliably use a fixed height.  Is there anyway to get panelbar to auto size (in the height direction mainly)?
 
Also, can it be done without building the stacker/panels in the head section (built in body).  Currently the stacker/panels work attached to an inline Dynlayer and built within the body. But I need to use a fixed height for the panel content.
 
Thanks for any advise.
 
-Bruce
 


www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Re: [Dynapi-Help] IOElement and cross domain urls

[donnaMarie g. <twi...@ya...>]

plaese don't send my anything anymore

Bruce Tennant <blu...@ya...> wrote:When you say "in synchronous"  what do you mean?  Only at initial page load?  
 
When I think synchronous, I think either a blocking fetch or some how aligned with another thread.  Just looking for a nominclature clarification.
 


Raymond Irving <xw...@ya...> wrote:

Yep! That's a security setting in the browsers. It's
called cross-domain scripting security.

The only way arround this is to use IOElementSync
class or FileReader to access the data in synchronous.

--
Raymond Irving

--- Bruce Tennant wrote:
> Maybe I missed this in the docs, but is there a
> known issue with grabbing a file from another
> domain?
> 
> When I grab a file from the same domain as the
> master page, no problems. But if the page is on
> another domain (even if an aliased ip address), it
> never reads it.
> 
> here's a test page
> 
> http://www.bluewolverine.com/fetch_page.html
> 
> The two urls it trys to grab are
> 
> local: http://www.bluewolverine.com/test.html
> remote: http://home.comcast.net/~bluewlvrn/test.html
> 
> same exact test.html file, both load when accessed
> directly from browser
> 
> 
> 
> 
> www.bluewolverine.com
> 
> ---------------------------------
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product
search


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Dynapi-Help mailing list
Dyn...@li...
https://lists.sourceforge.net/lists/listinfo/dynapi-help

www.bluewolverine.com

---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search


---------------------------------
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search